Upgrading apache

Davide Bianchi wrote:
 > Does your system works (meaning: it does what you want when you
 > want) ? If the answer is yes, DO NOT UPGRADE IT.
 >
 > Upgrade if and only if, your system doesn't do what you want when
 > you want, there is a bug that you always hit, the new version has
 > $feature that you really can't live without, the old version is
 > such a pain in the ass that upgrade is the best option _OR_
 > there is a huge security hole in the old version. Otherwise,
 > stick with what you have.

I know all that, but i'm a sucker for latest versions

Which way would you (or anyone else) recommend then?

Ben<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Upgrading apache 

"bengee" <postmaster RemoveThis @localhost.localdomain> wrote in message
news:ry6gc.33585$Y%6.4303901@wards.force9.net...

 > Which way would you (or anyone else) recommend then?

The way I would (and do) do it, is to build all the new versions in new
locations, then e.g. /usr/local/apache2-2.0.49 (this requires the use
of --prefix on all of them, and appropriate parameters to point each build to
the correct versions of each other where they need to link against each other).

Then once you are done switch your symlinks to point to the new ones from the
default locations.
e.g.
cd /usr/local
rm apache2 (assuming you used a symlink before, else rename this to the old
verion number)
ln -s apache2-2.0.49 apache2

Then in one easy batch of symlinks you have switched all these over, and not
upset anything that relies on their location. You can switch back just as easily
in case of a problem.

Richard.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Upgrading apache 

Richard Antony Burton wrote:
 > The way I would (and do) do it, is to build all the new versions in new
 > locations, then e.g. /usr/local/apache2-2.0.49 (this requires the use
 > of --prefix on all of them, and appropriate parameters to point each build to
 > the correct versions of each other where they need to link against each other).
 >
 > Then once you are done switch your symlinks to point to the new ones from the
 > default locations.
 > e.g.
 > cd /usr/local
 > rm apache2 (assuming you used a symlink before, else rename this to the old
 > verion number)
 > ln -s apache2-2.0.49 apache2

Thanks Richard, sounds good - i'll give that a try

Ben<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Upgrading apache