RHEL 7 beta

[Simone Caronni]

Hello,

On 30 January 2014 09:07, Nicolas Chauvet <kwizart at gmail.com> wrote:

> I would prefer to start using koji with el7 than plague, so not a priority
> given the amount of pending infrastrucuture tasks.
>  Also I'm still waiting for people interested in EL to show a working
> version of kmodtool/akmods.
>

I was working on it, but I expressed my concerns about the fact that akmods
are not really needed on RHEL on bug 2681 [1] but that received no reply.
I've also replied to a private email to you on the 9th of January about the
same concerns when you asked for the status but got no reply again.

Since it's quite related, I've also asked on the same mail of the 9th of
January for the third time (first two on -devel [2] [3]) if there's any
interest in separating again Nvidia open source tools from the drivers
before sending patches, because this goes back to the state they were
before removing open tools, but again I got no reply.

Here is an excerpt from the mail, I would like to hear some thoughts about
it before proceeding:

"I haven't touched it since christmas due to lack of time. I've invested
some time looking at how it is implemented in RHEL (I have an account) for
all the modules they ship to make it as close as possible as upstream, and
I've discovered it's an absolute mess and there's no ruling over it.

Kmodtool is contained in the redhat-rpm-config package (fedora / rhel),
inside the kmod rpms for old binary kmods (6.0/6.1 era) and in the latest
kmods they ship, they have kmodtool and every single other script used
copied over. And by looking at various modules I could see that none of
those scripts is equal in any redhat-rpm-config / kmod package, they are
all different.

An example of oracleasm.spec (RHEL 64 bit supplementary channel):
http://slaanesh.fedorapeople.org/oracleasm.spec

So I'm reverting to the idea of just patching the current RPMFusion's
kmodtool without looking at upstream.

Also I don't think akmods is really needed, we can ship a binary kmod
package, and that works and there is no need to rebuild it. As it is
released it will work until each RHEL release is supported. The only case
where we need akmods is for custom kernels, but if someone is able to
rebuild a custom kernel for RHEL then it is also able to rebuild the binary
kmod.

Example:

kmod-nvidia-331.20-1.el6.x86_64.rpm

Version 33.30 comes out, we ship the updated package:

kmod-nvidia-331.30-1.el6.x86_64.rpm

We don't need to rebuild it even if it's the last release ever out of
Nvidia, and we don't lose time rebuilding kmods every kernel update; so why
do we need akmods?"

Regards,
--Simone


[1] https://bugzilla.rpmfusion.org/show_bug.cgi?id=2681#c8
[2]
https://lists.rpmfusion.org/pipermail/rpmfusion-developers/2013-December/016117.html
[3]
https://lists.rpmfusion.org/pipermail/rpmfusion-developers/2013-December/016119.html




-- 
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).

http://xkcd.com/229/
http://negativo17.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.rpmfusion.org/pipermail/rpmfusion-developers/attachments/20140130/8ca306d4/attachment.html>