Hi, I wanted to try out the new and fabled TurboGears and found that it uses the new python software distribution tool setuptools and is distributed as python eggs. I can easily install it with setuptools/easy_setup, but I wanted to make an ebuild for TurboGears, which is not just so with setuptools and eggs. I started making ebuilds for the dependencies, but it seems that setuptools has a nasty habit of downloading dependencies for a package if it hasn't been installed by setuptools. So when eg. the new SQLObject 0.7rc1 (which also uses setuptools) depends upon FormEncode (not to mention depends upon setuptools) it does not care that I have already emerged setuptools or FormEncode, it just downloads the egg for it and installs it.
It seems that alot of python projects are starting to use setuptools/easy_install/eggs, and granted, it is quite neat, but there needs to figured out a way to handle installing these things through Portage, or alot of new versions are going to be a pain to have installed. How should Portage handle this? I was thinking that maybe hacking up a Gentoo specific version of setuptools that would make it work together with Portage or something like that, but it seems a bit un-gentoo-like. A different approach could be to grab the .egg files and manually install them in the ebuilds, which wouldn't be a problem for pure-python packages, but would suck for packages with c-extensions included, since some might end bound to a specific subset of archs. Instead of me just blindly fumbling in the blind for a way to get ebuilds for TurboGears and it's assorted dependencies, I thought it would be better to get some official guidelines. Some useful URLs: http://peak.telecommunity.com/DevCenter/setuptools http://peak.telecommunity.com/DevCenter/EasyInstall http://peak.telecommunity.com/DevCenter/PythonEggs -- Anders -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS/O d--@ s:+ a-- C++ UL+++$ P++ L+++ E- W+ N(+) o K? w O-- M- V PS+ PE@ Y+ PGP+ t 5 X R+ tv+ b++ DI+++ D+ G e- h !r y? ------END GEEK CODE BLOCK------ PGPKey: http://random.sks.keyserver.penguin.de:11371/pks/lookup?op=get&search=0xD4DEFED0 -- [email protected] mailing list
