On 06/29/2009 11:19 PM, Radu-Cristian FOTESCU wrote:
> * packages that are excluded from EPEL for legal reasons.
> RPM Fusion can hold them however and is meant to be
> compatible with EPEL.
If RPM Fusion is supposed to be "a better RPMforge", then
I beg to opine that it fails.
It doesn't really have any such goals and would still require among
other things a release engineer to move it forward. Hopefully it will be
in the near future. You are free to continue carrying whatever packages
you need in your repo meanwhile. This is why I suggested moving packages
in EPEL when there is a clear path to do so leaving the rest as it is,
> I suggest that you work with EPEL on packages that are
> cleanly in the first category initially.
Where would GIMP 2.3.15 fit into the picture? (Just an example.)
Does it conflict with the GIMP package in base EL? The EPEL policy is
not include packages that conflict with base EL packages. If it is
parallel installable, it might be acceptable.
The concepts, yes.
But do *I* sound reasonable? (Most often... not quite so.)
Seems so. The current structure is
EL = Core supported community
EPEL = Community supported extra packages
RPM Fusion = Packages excluded from EL and EPEL for legal reasons
You are right that EL portion of RPM Fusion is yet to take off well but
EPEL has good momentum that you can take advantage of.