RPM Fusion for EL (Was: Re: Supporting Moblin?)

[Eric Sokolowsky]

We use RHEL5 on our systems at work, and use the Nvidia binary driver. I'm
interested in maintaining packages that will install on stock kernels,
because it would make our job easier. I really only have access to x86_64
systems though. I may be able to package up i386 packages as well. Since I'm
coming out of the blue, I'd need guidance on where to submit packages.

-Eric

On Mon, Dec 14, 2009 at 2:55 PM, Jack Neely <jjneely at ncsu.edu> wrote:

> On Mon, Dec 14, 2009 at 08:34:19PM +0100, Thorsten Leemhuis wrote:
> > On 01.12.2009 22:44, Jack Neely wrote:
> > > On Wed, Nov 25, 2009 at 09:30:28AM +0100, Thorsten Leemhuis wrote:
> > >> Michel Alexandre Salim wrote on 25.11.2009 02:33:
> > >>> We've so far provided add-on packages for Fedora and RHEL;
> > >>
> > >> Nope, the latter was never really started and interest in it seems
> quite
> > >> low -- I likely sooner or later will suggest we drop it completely if
> > >> nobody steps up and feels responsible for it/takes care of it:
> > >>
> http://lists.rpmfusion.org/pipermail/rpmfusion-developers/2009-February/004058.html
> > >>> [...]
> > > I'll state that I'm interested in EL support from RPMFusion.  I'm
> > > planning on having some time toward this spring to work about getting
> > > some of the commonly used kernel modules my shop depends on for RHEL 6
> > > well maintained in RPMFusion.
> >
> > Sounds lame, but those that want to do it simply should start doing it,
> > otherwise RPM Fusion for EL afaics will fail before it even started for
> > real :-/
> >
> > IOW: There is nobody that will tell you "Yes, you have the job"; It's
> > more "just do it"
> >
> > IOW afain ;-) Just start doing some work to make RPM Fusion for EL
> > solid. Some ideas to start working:
> >
> > - check if all the deps in the current EL repo are satisfied and poke
> > package maintainers to fix it if not
> > - check if everything is working, if not, poke maintainers
> > - check if all the important packages people often want are in the EL
> repo
> > - owners.epel.list in our CVS is afaics not sully up2date
> > - work towards officially announcing RPM Fusion support for EL
> >
> > I's not my decision alone, but I'd be willing to hand someone the
> > signing keys for the EL repo, in case that someone
> >
> > - works on above list for at least a few weeks and thus shows he
> > committed to the "job"
> > - seems trust-able (e.g. ideally someone that is known in Fedora-land
> > already and not something new coming out of the blue)
> > - got access to the push server (which is something the Admins will have
> > to work out)
> >
> > Cu
> > knurd
>
> Kernel modules.
>
> That's what I'm interested in.  And for RHEL 5 that means (as we've
> mentioned earlier) kmodv1 kernel modules.  I would love to have the
> nvidia kmods available.  Would anyone be willing to help backport that
> or already have the goods in hand?
>
> I'd like to spend some time working toward EL6 rather than on 5.  But,
> EL6 doesn't seem to be very close.  I suspect more interest in EL-land
> once RHEL6 shows more signs of living.
>
> Jack
> --
> Jack Neely <jjneely at ncsu.edu>
> Linux Czar, OIT Campus Linux Services
> Office of Information Technology, NC State University
> GPG Fingerprint: 1917 5AC1 E828 9337 7AA4  EA6B 213B 765F 3B6A 5B89
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rpmfusion.org/pipermail/rpmfusion-developers/attachments/20091215/e4db3c17/attachment.html