Which is an annoying bit of process, but it would be quite possible to
exempt those packages from needing package reviews. It needn't take
that long.
Not needing reviews would help, but I wonder how hard it would be to make them children of python-PACKAGE. The main issue is the SRPM needs to have a different name so there is no conflict with the RHEL SRPM. That's easy to set in the spec file, but the build system requires the SRPM name to match the Fedora pkgdb and git names. Is it possible to define children, so python34-PACKAGE could use the same git repo as python-PACKAGE? This would be cleaner and more accurate than the current convention of creating a python3-PACKAGE git repo and pkgdb package.
Avram
_______________________________________________ epel-devel mailing list epel-devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
