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

[Chris Bainbridge]

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. As to your points:

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.

> RedHat and Mandrake have already "migrated" to rpm.  Does that mean Gentoo
> will be too in the near future?
> Sarcasm aside, 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. Whats the 
point in wasting effort backporting bug fixes when there are new releases? 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.

> I'm sure I'm not the only person who has no plans to migrate away from a
> working (and very stable!) Apache 1.3.x solution in the near future.  I
> have production servers running on this stuff, and being able to still use
> Apache 1 on Gentoo is important to my business.  Apache 1 & 2 installing
> into separate slots is great news (why doesn't 'USE="-apache2 apache"
> emerge -p apache' offer to install Apache 1 tho?  It offers to rebuild
> Apache 2 only.).  But already I'm coming across (unstable) ebuilds that
> have been written to only install with Apache 2 (even tho they're building
> software that works with Apache 1 as well).

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.


--
gentoo-dev@g.o mailing list