Am 10.10.2014 16:37, schrieb Gelonida N: > For Windows this would require a custom boot-loader
You may try softlinks on Windows. I heard rumors, NTFS supports them. >>> Other use case could be an alternative implementation of merge >>> by collecting all modules into a single .pyz/.pkg file, that will be >>> used by all the executables. >> >> Yes, absolutely. This would be a more elegant solution than the current >> MERGE(). The only problem is, that the scripts are part of the .pkg, >> too. But MERGE() has the same problem, so the solution should not be >> that hard to implement. > > Well for my given project no issue: There would be no naming clash as > the scripts, that I'd like to merge do share the same pythonpath, so > no name clashes for .pyc files would occur. But the *scripts* are part of the archive/.pkg, too. And *all* scripts in an archive/.pkg are executed in order. > But if I inderstand well I'd fall into the same issue than with thre > previous use case. the .pkg file would have the wrong name, no? No, this one is another issue. I suggest having a look at MERGE() and see what it does. (And again: we'd appreciate any pull-request .-) -- Schönen Gruß Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/openstreetmap-karten-in-typo3-einbinden Kolumne: http://www.cissp-gefluester.de/2012-01-in-die-cloud-in-die-cloud-aber-wo-soll-die-sein Goebel Consult ist Mitglied bei http://www.7-it.de/
smime.p7s
Description: S/MIME Cryptographic Signature
