Bug 431929 - Please add perl-Module-Versions-Report to the EPEL repos
Summary: Please add perl-Module-Versions-Report to the EPEL repos
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Module-Versions-Report
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Chris Weyl
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-02-07 21:05 UTC by Xavier Bachelot
Modified: 2008-02-14 00:24 UTC (History)
1 user (show)

Fixed In Version: 1.03-1.el5.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-02-14 00:24:15 UTC
Type: ---

Attachments (Terms of Use)

Description Xavier Bachelot 2008-02-07 21:05:46 UTC

There are people around that would like to see some of your Fedora
packages in Extra Packages for Enterprise Linux (EPEL) [1] -- I for
example would like to see perl-Module-Versions-Report in EPEL, which is
needed for rt3 (Request Tracker 3) and mainly send you this mail on
behalf of the EPEL team as you didn't yet let the team know via the
Contributor Status [2] page if you are planning to build some or all of
your Fedora packages for EPEL.

Are you interested in maintaining your packages in EPEL? EPEL is similar
to Fedora Extras -- just that EPEL is a add-on repo for RHEL and
compatible spinoffs such as CentOS. EPEL uses the same CVS and the same
build servers as Fedora and a lot of Fedora maintainers are EPEL
maintainers as well; the main difference is just that packages in EPEL
are updated more carefully and supported for a longer timeframe. See [3]
and [4] for details. In short: EPEL tries to ship a package once and
update it to later versions only when there is a strong need to.

For branching your packages for EPEL follow the standard Fedora
procedure[5] -- instead of FC-6 or F-7 targets just use EL-4 or EL-5 as
branch names. If you maintain several packages (> 2) you can also use a
scripted branching method (all packages from a contributor) by using the
scripted branch process[6].

If you are not interested in EPEL please let the EPEL contributors know
and update the information on [2] to avoid further mails like this --
that just takes a minute or two and would be a great help for the EPEL
team. Please note that EPEL maintainers that might want to see your
package in EPEL will likely start to maintain the package in EPEL sooner
or later and thus become co-maintainers [7] of your packages for EPEL.

The EPEL team appreciate your help with EPEL.









Comment 1 Stephen John Smoogen 2008-02-13 20:34:47 UTC
I think we can take this to be a 'not-interested' at the moment and move towards
the comaintainership branch for EPEL. 

Comment 2 Xavier Bachelot 2008-02-14 00:24:15 UTC
Branched and built for EL-5.

Note You need to log in before you can comment on or make changes to this bug.