On Tue, 2008-06-17 at 06:37 -0400, Toshio Kuratomi wrote: > So, eggs seem pretty straightforward to me. They establish what they > provide and what they depend on in their metadata. But the python() > namespace is not so easy. On the PackagingDraft/Python page I mention > that one thing we could try is to make a Provides: python(foo) for every > module in the site-packages directories. This is relatively > straightforward to automate but misses subpackages. The example I > brought up is bzr-gtk:: Aha, okay. I think that the right thing here is to get the first level and then we can later worry about the secondary case of subpackages. I mean, you could do Provides: python(bzrlib.plugins.gtk) or some-such, but I suspect that might get a bit out of hand. And I'm also not sure how common of a case it is to need to care about Jeremy -- Fedora-packaging mailing list Fedora-packaging@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-packaging
