httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <>
Subject Re: BETA binaries...
Date Mon, 11 Dec 2000 22:43:33 GMT
Apache should use Program Files unless otherwise instructed by the user.
That is the standard and the expectation in use today. Not using Program
Files would be analogous to not using /bin on a Unix box.


On Mon, Dec 11, 2000 at 01:47:05PM -0500, wrote:
> In a message dated 00-12-10 10:52:26 EST, you write:
> > This isn't guaranteed to be "c:\Program Files\Apache Group", since some 
> >  other directory name starting with Apache could already exist.  It is also 
> >  possible, though not very likely, that progra~1 could be something other 
> >  than Program Files.  The other place where this breaks down is when the 
> >  Apache Group folder doesn't exist yet.  In this case, you'd actually end 
> up 
> >  getting a directory named apache~1.
> If you read the whole message you will see that I personally
> don't see the reason for using "c:\Program Files\Apache Group\..."
> at all and would rather see c:\apache.1.3.15, etc, just like Perl does.
> Perl simply uses c:\Perl and doesn't play the 'Program Files' folder
> game... but at least for now the 'shortname' tip is an answer for 
> people reporting breakage in scripts.
> Sure... Directories need to be CREATED with long names
> if they don't exist, but for all the post-install scripts that break
> because of spaces in filenames the 'correct' short name will work.
> Yours 
> Kevin Kiley

Greg Stein,

View raw message