Wasn't Red Hat introducing something along the lines of a LAMP stack
that rolls on top of RHEL? LIke it would actually have PHP5/MySQL
5(or maybe 4.1) on top of RHEL 4. It was a separate subscription I
thought, but a valid idea. The latest software for what is needed,
and stable known-good software for the rest.
I thought something like that was talked about at the RH summit last year.
I do think that a rolling release on top of a no API/ABI breakage
release would be very difficult to do, and tend to agree that
targetting minor releases for updates probably makes the most sense
for users and developers.
On 3/1/07, Thorsten Leemhuis <fedora(a)leemhuis.info> wrote:
Matthias Saou schrieb:
> Tom 'spot' Callaway wrote :
>> On Thu, 2007-03-01 at 13:53 +0100, Axel Thimm wrote:
>>> On Tue, Feb 27, 2007 at 08:30:50PM +0100, Matthias Saou wrote:
>>>> FP! :-)
>>>> Joke aside, I'd like to see which views we have on the release and
>>>> update procedure to apply to EPEL.
>>>> - Do we want a moving (and potentially breaking) set of packages which
>>>> is constantly being updated?
>>> The CentOS way
>>>> - De we want a fixed set of packages when a RHEL release is made and
>>>> focus on major bugfixes and security updates from there on?
>>> More RHEL like
>> FWIW, the CentOS people I spoke to at FOSDEM were very much interested
>> in the "fixed set, with bugfixes and security updates only" model.
I agree with the "fixed set, with bugfixes and security updates only", too.
But also with this:
> ...but also in providing a lot of recent stuff. They already have php 5
> and mysql 5 in a separate location for people to use on CentOS 4.
But I'd say we should leave this out for now until EPEL lift of, and
find a a solution for this later.
Epel-devel-list mailing list