> I see your point. What happens if, someday, RedHat releases both an
> x.y and x.y+2 kernel for the same RH Release? Would they ever do
> that? In that case, should all the modules be in the same package?
Well maybe this happens (probably not this year :-) ). No one but RedHat could know if they would do so.
But if the modules can be build from the same source tree, I see no problems with including all the modules in one RPM.
openafs-kernel-<something>-rh.<version> could be designed to deliver the modules for stock and errata kernels of
a given RH version. I don't think it matters, if the kernels in there are both x.y and x.y+2 .
If we would need two different kernel-source RPMs for the different kernel versions, then we have to deliver
openafs-kernel-source-<AFS version>-rh.<RH version>.2<2|4|6> RPMs, but that's a another story.
Frank
----------------------------------------------------------------------
Dr. Frank Bagehorn
IBM Zurich Research Lab.
Saeumerstr. 4
CH-8803 Rueschlikon
Switzerland
----------------------------------------------------------------------
SMTP: [EMAIL PROTECTED]
Notes: Frank Bagehorn/Zurich/IBM@IBMCH
phone: ++41 (01) 724 83 23 fax: ++41 (01) 724 89 59
- [OpenAFS-devel] Re: Trial Baloon for Red Hat pac... Frank Bagehorn/Zurich/IBM
- [OpenAFS-devel] Re: Trial Baloon for Red Ha... Derek Atkins
- Re: [OpenAFS-devel] Re: Trial Baloon for Re... Frank Bagehorn/Zurich/IBM
- Re: [OpenAFS-devel] Re: Trial Baloon fo... Derek Atkins
- Re: [OpenAFS-devel] Re: Trial Baloon for Re... Jeremy Katz
- Re: [OpenAFS-devel] Re: Trial Baloon fo... Derek Atkins
