EPEL only packages? Review process?
Ray Van Dolson
rayvd at bludgeon.org
Sun Dec 7 15:57:37 UTC 2008
On Sun, Dec 07, 2008 at 10:42:41AM +0000, Paul Howarth wrote:
> On Sat, 6 Dec 2008 22:07:43 -0800
> Ray Van Dolson <rayvd at bludgeon.org> wrote:
> > Hi folks;
> > I recently submitted a package for review that is intended for EPEL
> > only:
> > https://bugzilla.redhat.com/show_bug.cgi?id=474430
> > Reason being that this python module is included already in Fedora,
> > but is not present in RHEL 4 or 5.
> > There wasn't really a procedure for this type of thing, so the product
> > I filed it under was the standard "rawhide".
> > Anything I should perhaps do differently in this case or am I going
> > about it in the right way?
> Isn't the procedure for this to ask the Fedora maintainer if they're
> interested in maintaining an EPEL branch for the package - if so, to
> branch and build it possibly with you as comaintainer, if not, add you
> as maintainer of a new EPEL branch?
Sorry, I should have clarified better. The uuid module I'm packaging
above is part of _python_ in Fedora (2.5 and newer?).
So this module doesn't fall under those guidelines... :)
More information about the epel-devel-list