On Thu, 28 Mar 2013 14:47:46 +0100, Thomas Spura wrote:
Bugzilla "component" names are the src.rpm %{name}s. You would first need to change that, so a pygtk2.src.rpm is not added to Bugzilla as "pygtk2" but with the names of (all?) its binary rpm(s) it builds.
What I meant is, that we have e.g.: python2-pygtk.src.rpm python3-pygtk.src.rpm pypy-pygtk.src.rpm
Hard to comment on, because that's not what packages do so far. It's more normal that a single src.rpm (in Fedora package git) builds multiple packages from a single source tarball. If a previously Python 2 based project adds compatibility for Python 3, you would reuse the tarball and not start a new src.rpm with a different name. Here, building for a newer Python version would require a new src.rpm -- it's probably a better idea to create front-ends for bugzilla which know about the mapping from binary rpms to source rpms.
The low-level details about RPM macros and virtual provides don't interest me yet, btw.