RPM Fusion for EL/EPEL 5

[Thorsten Leemhuis]

On 10.09.2008 17:27, Sebastian Vahl wrote:
> Thorsten Leemhuis schrieb:
>> More and more people talk to me and ask "when will RPM Fusion for
>> EL/EPEL 5 start". As a big junk of the livna import is now done I might
>> over the next few weeks slowly start to do the same work for EPEL. But I
>> need to know which of the package owners actually is willing to maintain
>> their packages in RPM Fusion's EL-branch.
>>
>> So if you want to maintain all or some of you packages for EL drop me a
>> line please. Then I'll create branches for them sooner or later and help
>> with the initial build round just like I do for Fedora now.
> 
> I assume that RPMfusion/EPEL is using the same guidelines for updating
> packages as EPEL itself? [1]

I'd say so.

> If so I'm not sure I'll be able to contribute. In a worst case scenario
> my package fails to build because a BR was updated for some reason (eg.
> serious security hole) and I'm not able to fix this (no programming
> skills here).

That of course can happen -- just like in can happen in Fedora as well. 
Okay, to be fair, it likely happens a bit more often in the EL branch -- 
especially if brand new and old stuff gets mixed together (which 
normally should not happen that often normally in the EL branch, as the 
EPEL policy suggest to only update packages to new versions if there is 
a really good reason).

In my experience the problem you outline happens quite seldom. And if it 
happens, then most of the time it's easy to find a workaround or patch 
to circumvent the problem. In the rare cases where programmings skills 
really are needed it's often not that hard to get help from upstream or 
other Fedora folks.

So the potential problem you outline is nothing I'd worry about.

CU
knurd