> #2 has the argument going for it that it follows previously approved > practice (perl, PHP). The pesky detail is that there is already Apache > 2.0 in /usr/apache2/.
And also, I think the general convention followed for multiple versions within a common product directory is to provide soft links to the latest version's bits from /usr/<product><major version> to /usr/<product><major version>/<version> e.g., For /usr/perl5/ drwxr-xr-x 5 root bin 512 Jun 9 2005 5.6.1 drwxr-xr-x 3 root bin 512 Jun 9 2005 5.8.3 drwxr-xr-x 5 root bin 512 Jun 9 2005 5.8.4 lrwxrwxrwx 1 root root 11 Jun 9 2005 bin -> ./5.8.4/bin lrwxrwxrwx 1 root root 9 Jun 9 2005 man -> 5.8.4/man lrwxrwxrwx 1 root root 15 Jun 9 2005 pod -> ./5.8.4/lib/pod drwxr-xr-x 4 root bin 512 Jun 9 2005 site_perl drwxr-xr-x 5 root bin 512 Jun 9 2005 vendor_perl This cannot be done for Apache if we go with apache2/<version> layout structure. -- Seema.
