[Fedora-packaging] Python Egg Guidelines

[Toshio Kuratomi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,
I've finished a first draft of guidelines for using python eggs.
There's one open question -- whether we should be creating eggs for
upstreams that do not create them by default.  I think the answer to
that is no except for one special case but others might disagree.

The rest of it is pretty straightforward; made longer by the addition of
copious examples.  Take a look and give feedback.  The Packaging
Committee will vote on this on Tuesday (next week's packaging meeting.)

  https://fedoraproject.org/wiki/PackagingDrafts/PythonEggs

PS: We already have a couple of cases where we need to apply these
guidelines
  * Review for parallel installable python-sqlalchemy0.3:
  https://bugzilla.redhat.com/show_bug.cgi?id=257381

  * Request for python-cherrypy-3.0 upgrade which needs a
python-cherrypy2 compat package for TurboGears.
  https://bugzilla.redhat.com/show_bug.cgi?id=224683

  * Request to add egginfo to docutils (which is a departure from upstream).
  https://bugzilla.redhat.com/show_bug.cgi?id=256541

- -Toshio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFG1MfaX6yAic2E7kgRAmIlAJkBMOooviBZHGZhkg+Anh5kBQvDkACeIXLq
poCNwcUzHDbE8DN8EHU+58g=
=NZPE
-----END PGP SIGNATURE-----