New (optional) python egg dependency generator for RPM

[Jason L Tibbitts III]

>>>>> "NC" == Nick Coghlan <ncoghlan at gmail.com> writes:

NC> If so, then there's some relevant work currently under way upstream
NC> to improve the interaction between Python installation tools and
NC> build systems to improve the metadata extraction process, rather
NC> than relying on implementation details of setuptools.

If that's the case, could someone bang out a few paragraphs that we
could use as a blueprint for some packaging guidelines?  An example
spec, or even just the file layout and some idea of how autogenerated
dependencies would work would be enough.  I know this stuff is a bit
new, but we've been doing a really big overhaul of the python stuff and
we'd like to at least design to accommodate this rather than having to
do it all over again once this new format comes out.

 - J<