-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Draft 2 of the new Egg guidelines. I'm continuing to test things out so things might change a little. However, these are my current thoughts on how we can best use eggs in the distro and even if they change in specifics of spec file scripts, the general thrust is going to remain the same. http://fedoraproject.org/wiki/PackagingDrafts/PythonEggs The basics are: Support eggs for all distutils and setuptools packages from f8 on. This depends on us reverting to upstream python WRT distutils in python-2.5. Jeremy, I've started testing what this changes but I need your input on whether we can make this change or not. Support for eggs for setuptools and distutils-only-when-required to make other packages work on f7 and below. Support for multi versions through eggs knowing that there's no API within setuptools that is "reliable" for making switching of versions work. A quick and dirty method that hacks the PYTHONPATH and involved method that makes using setuptools mandatory are documented as well as the problems that could occur with pkg_resources.require() and __require__. - -Toshio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFG5d6lX6yAic2E7kgRArK5AJkBoBY2CD7m8sBCcS5JhVLyNappSQCfaAob vs5J5Z1+ORHjChflnyIbhkg= =le7v -----END PGP SIGNATURE----- -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
