Hi Giovanni, thanks for the constructive discussion :-)
I'll start with the end (because this is my aim). > I think I'm missing something here -- are your projects standalone > Windows applications (which just happen to be written in Python), or are > they Python packages meant for a Python developer to be used? [..] > The distutils package provides support for building and installing > additional modules into a Python installation. My program is both an application and a package, but the "application" part is the more important. This is why I need to build a Windows package. So you are right: distutils are the wrong tool! I should better go this way: first install the package in wine, then bundle it from the files generated there. For uploading to Origo, I'll have to implement a separate step afterwords. Thanks for opening my eyes. Thus feature #2 is not necessary. Regarding feature #1: Since the main reason for implementing this would have been feature #2, which is now gone, I see not that much benefit for #1 any more. Nevertheless I'm going to answer you questions: > How do you propose to change the way PyInstaller is executed by the user > when installed through pip/easy_install? I propose no change here. Configure.py, Build.py, et al at installed scripts, that's all. > Where do you plan to move config.dat, which is currently created by > Configure.py, and couldn't be created in site-packages which is not > user-writable in UNIX systems? And what about the bincache directories? I did not think about these until now. Since distutils do not support post-install scripts, config.dat can not be generated when the package is installed. So unfortunately it needs to go to $HOME. bincache need to go there, too. How is this solved in RPM od DEB packages now? > [[ BTW I think we could eventually move away from Configure.py > altogether -- I don't see such a gain from having a separate So at least one of these issues would be solved :-) > My own plan to cover the distribution step is to have a separate binary > (Deploy.py, to be run after Build.py) which would: > > * Windows: create an installer through InnoSetup, packaging all the > required files discovered by Build.py plus user-defined files. > * Linux: create a DEB or RPM. > * Mac: create a DMG. Hey, this would be great! [BTW: NSIS can be crossbuild on Linux/Unix Systems, so it *may* be preferable to Innosetup.] > working quite well, but it's under a proprietary license at the moment. > I'm working towards making it GPL and releasing it. This sounds even better :-) Any way to help out? -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP, CSSLP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de Monatliche Kolumne: http://www.cissp-gefluester.de/ Goebel Consult mit Mitglied bei http://www.7-it.de
smime.p7s
Description: S/MIME Cryptographic Signature
