<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top"><p dir="ltr">an idea</p>
<p dir="ltr">When changing the link to point to newer version, create a new centos-release package for the old one that mention is not supported, like 6.5.notsupported</p>
<p dir="ltr">This way people who only use the version specific repo will get a last update <br>
If they never update then they dont care much and the change we are discussing is not relevant for them</p>
<p dir="ltr">Thanks<br>
roger</p>
<p dir="ltr">Sent from Yahoo! Mail on Android</p>
</td></tr></table> <div id="_origMsg_">
<div>
<br />
<div>
<div style="font-size:0.9em">
<hr size="1">
<b>
<span style="font-weight:bold">From:</span>
</b>
Jim Perrin <jperrin@centos.org>; <br>
<b>
<span style="font-weight:bold">To:</span>
</b>
The CentOS developers mailing list. <centos-devel@centos.org>; <br>
<b>
<span style="font-weight:bold">Subject:</span>
</b>
Re: [CentOS-devel] CentOS 7 and release numbering <br>
<b>
<span style="font-weight:bold">Sent:</span>
</b>
Fri, Jun 20, 2014 8:09:56 PM <br>
</div>
<br>
<table cellspacing="0" cellpadding="0" border="0">
<tbody>
<tr>
<td valign="top"><br clear="none"><br clear="none">On 06/20/2014 02:52 PM, Nathanael D. Noblet wrote:<br clear="none"><br clear="none">> So this is the clearest explanation - not sure why it wasn't clearer to<br clear="none">> me earlier. I mean I got the basic idea, once RHEL moves on to a newer<br clear="none">> point release updates to their previous point releases costs money and<br clear="none">> is not available for CentOS to rebuild and maintain an identical tree.<br clear="none">> <br clear="none">> So as a user that has never paid for RHEL I wasn't 100% aware that this<br clear="none">> existed. I've always basically kept my systems up to date just assuming<br clear="none">> that the point releases were kind of like Microsoft's Service Pack X.<br clear="none">> Having never paid for a fix to be ported to a previous Service Pack<br clear="none">> level its not
till today that it makes sense that MS would allow clients<br clear="none">> to pay for that kind of service.<br clear="none">> <br clear="none">> All this to say is that I never thought I could stay on a point release.<br clear="none">> Also I'm wondering if someone doesn't update the centos-release-6.5 rpm<br clear="none">> won't they still be getting updates anyway? I just checked it it looks<br clear="none">> like you are. <br clear="none"><br clear="none">We handle this by pointing the yum repositories at the major version. So<br clear="none">/6/ instead of /6.5/ for example. When 6.6 comes out, we'll alter the<br clear="none">symlink to point /6/ to the 6.6 tree instead of the 6.5 tree.<br clear="none"><br clear="none">The problem with this is that you'll either have users who NEVER update,<br clear="none">or they update but never know what version they're on.<br clear="none"><br clear="none">The users
who don't update tend to fall into two camps:<br clear="none"><br clear="none">1. It's working, DON'T TOUCH IT!<br clear="none"><br clear="none">2. My vendor for $foo told me it's only supported on this one specific<br clear="none">version so I'm staying there no matter what.<br clear="none"><br clear="none">> Here's my simplistic suggestion, don't maintain those older trees. One<br clear="none">> tree lastest version for the major version. This is the clearest signal<br clear="none">> that there is only ever one area where updates occur. Or if there is a<br clear="none">> good reason to keep older packages in their own point release, make the<br clear="none">> centos-release always point to the 'latest' repo. As in it doesn't<br clear="none">> matter if I have centos-release-6.2/6.3/6.4 they always point<br clear="none">> at /repo/latest?<br clear="none">> <br clear="none"><br
clear="none">That's mostly what we do, via the symlink method explained above.<br clear="none"><br clear="none">On our mirrors, we only keep the latest tree. We do however archive<br clear="none">legacy trees on the vault mirrors so that people who need to duplicate<br clear="none">an environment from a given time period can do so. You'd be amazed how<br clear="none">often people have to recreate the past.<br clear="none"><br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Jim Perrin<br clear="none">The CentOS Project | <a shape="rect" href="http://www.centos.org" target="_blank">http://www.centos.org</a><br clear="none">twitter: @BitIntegrity | GPG Key: FA09AD77<div class="yqt1664598591" id="yqtfd76964"><br clear="none">_______________________________________________<br clear="none">CentOS-devel mailing list<br clear="none"><a shape="rect" ymailto="mailto:CentOS-devel@centos.org"
href="javascript:return">CentOS-devel@centos.org</a><br clear="none"><a shape="rect" href="http://lists.centos.org/mailman/listinfo/centos-devel" target="_blank">http://lists.centos.org/mailman/listinfo/centos-devel</a><br clear="none"></div></td>
</tr>
</tbody>
</table>
</div>
</div>
</div>