Am 16.01.2016 um 19:10 schrieb Nicholas Chammas: > The specific things I’m looking to see examples of in other people’s > projects are:
You may have a look at brog -backup: https://github.com/borgbackup/borg > * How do they invoke PyInstaller? If they use a |.spec| file, what > does it look like and do they check it in to their VCS? > As long as you can pass all required parameters on the command line, I'd suggest *not* using a .spec-file. This eases updating for the case the .spec-file would change or get new features. > * Do they restructure their project in any way to better support > PyInstaller? > If you are using virtual environments, this should not be necessary. Just setup the virtual env, install everything required into it, an run pyinstaller. > * Do they use CI services like Travis and AppVeyor to automatically > test their packaging process and generate release artifacts for > the various OSes? > borg backup uses travis and Vagrant. (I personally find the later one very interesting and adopted it for building PyInstallers bootloader.) -- 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/verschlusselte-mailingslisten Kolumne: http://www.cissp-gefluester.de/2011-02-fleisige-datensammler-fur-lukratives-geschaeftsmodell-gesucht -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyinstaller+unsubscr...@googlegroups.com. To post to this group, send email to pyinstaller@googlegroups.com. Visit this group at https://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
