Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 7397 invoked by uid 6000); 10 Aug 1999 19:46:59 -0000 Received: (qmail 6955 invoked from network); 10 Aug 1999 19:46:39 -0000 Received: from cookie.covalent.net (208.214.57.1) by taz.hyperreal.org with SMTP; 10 Aug 1999 19:46:39 -0000 Received: (from daemon@localhost) by cookie.covalent.net (8.9.1a/8.9.1) id OAA06924 for ; Tue, 10 Aug 1999 14:46:31 -0500 (CDT) (envelope-from randy@covalent.net) Received: from blanca.covalent.net(192.168.2.5), claiming to be "blanca" via SMTP by mail.covalent.net, id smtpdC14537; Tue Aug 10 14:46:26 1999 From: "Randy Terbush" To: Subject: RE: Win32 Install Paths Date: Tue, 10 Aug 1999 14:46:26 -0500 Message-ID: <009901bee369$083c66c0$0502a8c0@covalent.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: <4.2.0.58.19990810142806.09e64a20@post> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Status: O > > Can you just not put anything in the registry at all? The > registry is a > very evil thing and great lengths should be taken to avoid > it whenever > practical. With Apache being a cross-platform project, > wouldn't it make > more sense to do as much as practical in a cross-platform > fashion? What > other platforms have a registry? > > Also, paths that do not conform to 8.3 naming often cause > problems. Sure > the problems are mostly with M.S. programs (like > installers, etc), but > there are tools and what-nots that do not like paths not > conforming to 8.3 > naming. Also, who wants to have to type all of that in > every time they > happen to need to type in a path? That name is very (very > very very very) > long and consumes much horizontal space - is that really > necessary?? It > will be a nuisance with Explorer, etc. and part(s) of it > will simply not be > visible in text areas that display path names in some programs. Try as you might, fighting against conventions for that platform is not practical. I don't like it any more than you do, but don't see a reason to fight it. > > Perhaps you are trying to be cute? I would recommend you > try really hard > to be practical instead. Don't be a smart ass. I'm following some given conventions. The current layout for our distributions are: \Program Files\Apache Group\Apache The above does not fit into the future of this group given the name change and possible other "Apache" software projects that will go under that directory. I like Ryan Bloom's suggestion and will head in that direction. > > Also, are you saying automatically put it there (or in some > more practical > directory) no matter, or would there be an option to > install it where ever > the user chooses? There really has to be an option - > stuffing programs on > somebodies C drive without choice is a very evil thing do > to them. For one > reason, it is a common design to have the C volume be very > small, and place > applications, etc on other volumes that are designed to have > applications. Such designs can have numerous advantages, > and inflicting a > person who has smartly designed their computer with a small > C drive is > really not nice at all. > > > At 01:59 PM 8/10/99 -0500, Randy Terbush wrote: > >As I pull the last pieces of this Win32 installer > together, do we want > >to consider the following new paths for files and registry > entries to > >reflect recent changes in this project? (barf bags ready) > > > >\Program Files\Apache Software Foundation\Apache Web Server\ >