RE: [gentoo-dev] HEADS UP: Twitching to un-arch-mask Apache2

["Stuart Herbert" <stuart@myrddraal.demon.co.uk>]

Hi Chris,

> I don't think software updates should be held back because 
> people might still 
> be using old versions. You can fix your apache1 installation 
> now, and all of 
> the software you currently have installed will continue to 
> work. You just 
> won't be able to use new packages that require apache2. 

You're making the assumption that ebuilds for packages that support apache1
continue to support apache1 in the future.  If, say, the mod_php ebuild
drops support for apache1, then that forces mod_php users to upgrade to
apache2.  It'll happen eventually, sure.  It seems reasonable enough to ask
whether the gentoo devs have a plan to do this sooner tho ;-)

> On Monday 23 June 2003 11:11, Stuart Herbert wrote:
> >
> > PHP is still not recommended for production use with Apache 2 
> > (http://www.php.net/manual/en/install.apache2.php).
> 
> <shrug>. AFAIK gentoo isn't recommended for production use either.

Not my issue.  The nice thing about Gentoo is that it's a
"meta-distribution"; it allows us to build servers up out of software that
we - as the responsible sys admins - are prepared to use in production.
Personally, I'm happy continuing to use apache1 for now, but am not ready to
move to apache2.  I'm not trying to stop anyone else from using apache2
(like I could anyway!).  I'm just interested in understanding what the
future is for apache1 support on Gentoo.
 
> is 
> "keeping up 
> > with the Jones's" really that important?
> 
> Yes, actually it is. One of the compelling reasons for my switch from 
> debian/redhat to gentoo was that the packages are more 
> up-to-date. 

Same here.

But "packages up to date" isn't the same as "default choice = what other
distros do".

> Whats the 
> point in wasting effort backporting bug fixes when there are 
> new releases? 

Who's backporting bugfixes where?  I don't see how making apache2 the
default web server has anything to do with any issues around backporting
bugfixes.

> If 
> you need this kind of "fixed point release" software then 
> gentoo, with its 
> constant upgrade cycle, probably isn't the best distro for you.

Thank you for the advice, but I'll decide what's the best distro to run on
my servers, thank you very much.    The reason I like Gentoo is that, I
feel, it offers a far wider choice than the other distros.  

I'm not asking for "fixed point releases".  You've misunderstood me.  All
I'm asking is whether mods will continue to build for apache1 for the
future.  Not just apache1, but important "value added" packages like mod_php
and mod_authmysql.
 
> You can't hold back progress. Having said that, all of your 
> existing software 
> will continue to work as long as you choose not to upgrade 
> it. With gentoo, 
> its your choice.

I'm not trying to hold back progress.  I'm just trying to understand what
the apache1 position will be going forward.  What's wrong with that?  Do you
feel threatened somehow by the idea that there's someone out there who isn't
enthusiastic about running apache2 yet?  Why the strong (and negative)
reaction to practical questions?  

Thanks for the feedback Chris, but please - next time read what I've said
before hitting that reply button.

Best regards,
Stu
--



--
gentoo-dev@gentoo.org mailing list