-----BEGIN PGP SIGNED MESSAGE-----
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.)
PS: We already have a couple of cases where we need to apply these
* Review for parallel installable python-sqlalchemy0.3:
* Request for python-cherrypy-3.0 upgrade which needs a
python-cherrypy2 compat package for TurboGears.
* Request to add egginfo to docutils (which is a departure from upstream).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----