> ----- Original Message ----- > From: "Guy Hulbert" <[EMAIL PROTECTED]> > To: [email protected] > Subject: Re: Eliminating absolute paths on installation > Date: Wed, 13 Dec 2006 08:16:08 -0500 > > > On Wed, 2006-13-12 at 13:16 +0100, Paul Fee wrote: > > This is a problem for me as the install location is not always known > > at build time. Also, if I give someone a built version of httpd, they > > can not install it multiple times on one host due to the absolute > > paths. > > Why do they need more than one ? > > -- > --gh
Hi Guy, The main motivation is that I don't want to dictate install location to people that are using my builds of httpd. Secondly, I have multiple people testing httpd and my module. I want to increase machine utilisation and allow multiple installations on one box. It may be possible to arrange that they share a common httpd but ideally each installation would be self contained. For example different httpd versions may be built with different options. The only conflicting resource that different instances must avoid contention over should be the TCP port that httpd listens on. Another scenario would be a httpd server in active service and the need to install a new version (in a different directory) for testing without removing the active version. It would be good if httpd had the option to be built without advanced knowledge of its install location. Without eliminating absolute paths, I find myself heading down the path of OS visualisation, which to me seems very heavy weight to install multiple instances of one application. Thanks, Paul -- _______________________________________________ Surf the Web in a faster, safer and easier way: Download Opera 9 at http://www.opera.com Powered by Outblaze
