[repo-coord] Packaging Dilemma

[Jeff Pitman]

Hi:

I'm not 100% decided on the PyVault nomenclature, but in the meantime 
I've run into something that's made me frown :( because it runs against 
my goals for the PyVault repo.

/usr/share/pygtk/2.0/* is my bane.  But, others come into play as well, 
such as /usr/include/pygtk-2.0/, /usr/lib/pkgconfig/*.  These files are 
usually from a set of -devel packages.  The ones specifically that I am 
building are gnome-python, pygtk2.  I wanted to make sure that 
installed files were totally separate so that these packages could 
co-exist with other Python library packages that were attached to 
another version of Python, say 2.2.2.  I want to avoid Provides: 
because I'm afraid that the redhat-config-* family will get goofed up.  
These config programs require pygtk2.  Currently, I'm naming it 
python2.3-pygtk2 ... .rpm.

Thoughts?

-- 
-jeff