www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From p..@apache.org
Subject Re: os-windows/3741: custom install does not set up conf directory
Date Sat, 23 Jan 1999 15:34:04 GMT
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

Synopsis: custom install does not set up conf directory

State-Changed-From-To: open-suspended
State-Changed-By: pcs
State-Changed-When: Sat Jan 23 07:34:03 PST 1999
Thanks for the comments.

First, the "custom" install is intended to allow advanced
users to choose to not install (say) the manual while still
getting the source. Almost every other situation is covered
by the typical or full installations, which most people
should use.

The custom install does work, but it is possible to 
deselect components which are required for Apache to
operate. In particular, if you deselect "Application Files"
you won't get any binaries or standard configuration files,
and if you deselect "Required directories" you won't get a
"conf" directory or any pre-configured configuration files.
Users that deselect components with key names such
as "Application Files" or "Required directories" are
assumed to know what they are doing. 

Secondly, about adding an icon for stopping Apache. This
is a good idea. It would be nice to not install the
start/stop Apache icons on Win NT (where they are not needed
since the SCM can be used), but I don't think that
InstallShield Express 2 can do that. 

I've marked this PR as "suspended" as a reminder to add
a "stop Apache" icon.

View raw message