[OpenAFS-devel] Re: Trial Baloon for Red Hat packaging

Frank Bagehorn/Zurich/IBM fba@zurich.ibm.com
Wed, 26 Sep 2001 18:09:51 +0200


This is a multipart message in MIME format.
--=_alternative 0058CAC6C1256AD3_=
Content-Type: text/plain; charset="us-ascii"

> 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: fba@zurich.ibm.com
Notes: Frank Bagehorn/Zurich/IBM@IBMCH
phone: ++41 (01) 724 83 23  fax: ++41 (01) 724 89 59

--=_alternative 0058CAC6C1256AD3_=
Content-Type: text/html; charset="us-ascii"


<br><font size=2 face="Courier New">&gt; I see your point. &nbsp;What happens if, someday, RedHat releases both an<br>
&gt; x.y and x.y+2 kernel for the same RH Release? &nbsp;Would they ever do<br>
&gt; that? &nbsp;In that case, should all the modules be in the same package?<br>
</font>
<br><font size=2 face="sans-serif">Well maybe this happens (probably not this year :-) ). No one but RedHat could know if they would do so.</font>
<br><font size=2 face="sans-serif">But if the modules can be build from the same source tree, I see no problems with including all the modules in one RPM.</font>
<br><font size=2 face="sans-serif">openafs-kernel-&lt;something&gt;-rh.&lt;version&gt; could be designed to deliver the modules for stock and errata kernels of</font>
<br><font size=2 face="sans-serif">a given RH version. I don't think it matters, if the kernels in there are both x.y and x.y+2 .</font>
<br><font size=2 face="sans-serif">If we would need two different kernel-source RPMs for the different kernel versions, then we have to deliver</font>
<br><font size=2 face="sans-serif">openafs-kernel-source-&lt;AFS version&gt;-rh.&lt;RH version&gt;.2&lt;2|4|6&gt; RPMs, but that's a another story.</font>
<br>
<br><font size=2 face="sans-serif">Frank</font>
<br><font size=2 face="sans-serif"><br>
----------------------------------------------------------------------<br>
Dr. Frank Bagehorn<br>
IBM Zurich Research Lab.<br>
Saeumerstr. 4<br>
CH-8803 Rueschlikon <br>
Switzerland<br>
----------------------------------------------------------------------<br>
SMTP: fba@zurich.ibm.com<br>
Notes: Frank Bagehorn/Zurich/IBM@IBMCH<br>
phone: ++41 (01) 724 83 23 &nbsp;fax: ++41 (01) 724 89 59</font>
<br>
--=_alternative 0058CAC6C1256AD3_=--