Anyone with a RHN Satellite Server can do the entite media history from the Kickstartable Trees in 5 minutes. I.e., I've done it many times over the years, even recently off-list to many.
What I've heard is that some here will only accept a specific, actual statement from Red Hat on its own entitlement history. So doing such, which I've also done, is moot. I.e., we continue to have a lot of interpretation.
On Fri, Jun 15, 2012 at 5:14 PM, Toshio Kuratomi <a.badger@gmail.com> wrote:
> If you can list for us what actual channels are the equivalent of the old
> AS/AP then we have something else that we can try to use to define logically
> which channels should not be overlapped with. If you've found this
> information somewhere then giving it to us will be a valuable addition to
> the conversation. Otherwise, we'll have to continue to assume that there
> isn't an actual understanding of what that is and we'll have to continue to
> try to define it ourselves with a somewhat arbitrary division.
I am willing to do some work here to attempt to sort this out since I
think having a clear policy that EPEL users understand is worth the
bother. I have media going back to RHEL3 and can sort through what
came on it, which I think is a fair definition of what is part of
"RHEL" proper prior to the release of RHEL6.
I do want to observe that there was a media change in RHEL5 which
added some things to the media which required entitlements that go
beyond a RHEL server subscription so there is a transition point of
sorts at RHEL5. At a glance I'm guessing this added several items
which include clustering and GFS, load balancing, and some
virtualization bits.
Another observation that is important is that "comes on the
installation media" doesn't cut it any more with the release of RHEL6
since half of RHEL6 isn't distributed on media due to its size growing
so dramatically but simply adding the optional channel to what RHEL6
media contains seems to me to include what previously would have been
distributed via the media with the possible exception of some or all
of the Add-On channels which also may have been included on RHEL5
media.
So one question I have is whether it is worth the effort to go back
beyond RHEL5 when looking at this now? Since Red Hat changes this up
every release I doubt EPEL should be bound forever by whatever Red Hat
did in 2004. Where do we want to draw the baseline now?
John
_______________________________________________
epel-devel-list mailing list
epel-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/epel-devel-list