From: Philip Kovacs <kovacsp3@co...> - 2005-09-23 00:25:55
I believe a better way to make the byte-compiled (.pyc) versions of the
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
(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:
In lieu of a proper setup.py, I would perhaps consider simply writing
(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
let python create the .pyc files as it installs the modules. I'm not
any gentoo eclass to do this work is the right direction. Maybe the
can chime in on that.
I will cc: the setup.py suggestion upstream for consideration with the
maintainers (fellas, this is a gentoo distro discusssion.)
Peter Hyman wrote:
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.
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.
Get latest updates about Open Source Projects, Conferences and News.