From: Hartmut Goebel > Am 04.01.2011 18:51, schrieb Martin Zibricky: > > Do you think it could be beneficial to provide .rpm or .deb packages? > Sure, it's always good to easy users life and help them staying with > what they are used to. And even developers are used to RPMs/DEBs. They > will get them scripts in the PATH while still being able to remove all > of it easily. > > Are you willing to start with it? > That's why I'm posting :-) > > We have to decide on the name of the scripts put into /usr/bin/, since > "Build.py" is not such a good name IMHO. What do you prefer: > > pyiBuild > pyi-build > pyinstaller-build > pyinstallerBuild > > There will be some work to be done to ease patching the pathes with in > the pyinstaller files (HOME will not be enough). But this is > just a bit > of cleanup which should be done anyway.
i've called my command line frontend to PyInstaller "pyi". see it attached. % pyi pyi command args... available commands: help display this text show display configuration build process spec file mkspec create spec file reconf configure pyinstaller it doesn't need any changes to PyInstaller itself. while we're at it: i'd prefer PyInstaller to do as eg. Docutils does with rst2*.py frontends. -- roman -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
pyi.sh
Description: pyi.sh
