From: Philip K. <kov...@co...> - 2005-09-23 00:25:55
|
Peter, I believe a better way to make the byte-compiled (.pyc) versions of the python modules, if that is your goal, would be for the upstream maintainers of rox-filer/rox-lib to distribute the software with a setup.py which calls the "setup" function within the distutils package (module: core) included with python itself. The setup.py module could then be invoked by the ebuild along these lines: python setup.py install --prefix=/usr/lib (or some other variant) as part of the installation. Ref: http://www.python.org/doc/2.3.5/inst/inst.html. In lieu of a proper setup.py, I would perhaps consider simply writing one yourself (they are painfully simple), and including it in the files/ subdir of the portage dir for rox-lib. Then invoke this home-grown setup.py file from within the ebuild and let python create the .pyc files as it installs the modules. I'm not sure changing any gentoo eclass to do this work is the right direction. Maybe the gentoo devs can chime in on that. I will cc: the setup.py suggestion upstream for consideration with the rox-filer/rox-lib maintainers (fellas, this is a gentoo distro discusssion.) Phil Peter Hyman wrote: Sergey, I have submitted well over a dozen rox ebuilds as well as an eclass fix (this actually is quite important) for review and inclusion in portage. |
From: Philip K. <kov...@co...> - 2005-09-23 02:18:24
Attachments:
setup-2.0.2.txt
|
By distributing a file such as the one attached below (rename it to setup.py), installers can invoke the command (or similar): python setup.py install --install-purelib=/usr/lib/ROX-Lib2/python/rox/ to create .pyc byte-compiled versions of the .py modules in that diectory. Phil |