Alan DuBoff wrote:

> Stefan,
> 
> Your suggestion above might be the best.
> 
> The other thing is, what about having 2 seperate directories, keeping the old 
> and adding the new, and using a symlink to point to the desired version.

This was one of the other suggestions made on the ARC discuss list. My primary 
concern about keeping both 2.0.x and 2.2.4 around (albeit temporarily) is that 
it creates the possibility of a huge disaster:

application <X> links againsr /uar/apache2
application <Y> links against /usr/apache2.2
application <Z> links against <X> and <Y>

If this were ever to happen, it would be discovered quite quickly (i'm willing 
to bet that any apache module linked in such a dysfunctional fashion will crash 
very quickly).

The question then becomes: in the interest of preserving Sun customers' 
existing 
installations, easing the transision pain, and giving enough leeway for module 
porting and regression testing, is the possibility described above an 
acceptable 
risk ?

--Stefan

-- 
Stefan Teleman
Sun Microsystems, Inc.
Stefan.Teleman at Sun.COM


Reply via email to