You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brian Behlendorf <br...@hyperreal.org> on 1998/05/20 05:42:50 UTC

Some Win32 release stuff....

1) could we change access_log and error_log to access.log and error.log in the
.conf-dist-win files?

2) can we change the .conf-dist-win files to simply be .conf files when the
Win32 release gets built?  it avoids the clunky "first you have to rename
such-and-such... yes, I know that file already exists..."

	Brian


--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction                                  brian@apache.org
                                                        brian@hyperreal.org

Re: Some Win32 release stuff....

Posted by Ben Laurie <be...@algroup.co.uk>.
Brian Behlendorf wrote:
> 
> At 12:38 PM 5/20/98 +0000, Paul wrote:
> >However I would much prefer to see us install the manuals into a top-level
> >manuals directory, and add "Alias /manuals @@ServerRoot@@/manuals" to
> >httpd.conf. They we could always safely upgrade the user's manuals without
> >touching their document root.
> 
> That seems like a good idea, yes.  Go ahead and do this for 1.3b7 win32
> build if you want, we can think about doing this for 1.3.0 final next week.

BTW, speaking of Win32, I've been told that msvcrt.dll was missing from
the 1.3b6 distribution - is that fixed?

Cheers,

Ben.

-- 
Ben Laurie            |Phone: +44 (181) 735 0686|  Apache Group member
Freelance Consultant  |Fax:   +44 (181) 735 0689|http://www.apache.org
and Technical Director|Email: ben@algroup.co.uk |
A.L. Digital Ltd,     |Apache-SSL author    http://www.apache-ssl.org/
London, England.      |"Apache: TDG" http://www.ora.com/catalog/apache

Re: Some Win32 release stuff....

Posted by Brian Behlendorf <br...@hyperreal.org>.
At 12:38 PM 5/20/98 +0000, Paul wrote:
>However I would much prefer to see us install the manuals into a top-level
>manuals directory, and add "Alias /manuals @@ServerRoot@@/manuals" to
>httpd.conf. They we could always safely upgrade the user's manuals without
>touching their document root.

That seems like a good idea, yes.  Go ahead and do this for 1.3b7 win32
build if you want, we can think about doing this for 1.3.0 final next week.

	Brian


--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction                                  brian@apache.org
                                                        brian@hyperreal.org

Re: Some Win32 release stuff....

Posted by Martin Kraemer <Ma...@mch.sni.de>.
On Tue, May 19, 1998 at 09:42:50PM -0700, Brian Behlendorf wrote:
> 
> 1) could we change access_log and error_log to access.log and error.log in the
> .conf-dist-win files?

    +1. Avoids many M$-related problems.

> 2) can we change the .conf-dist-win files to simply be .conf files when the
> Win32 release gets built?  it avoids the clunky "first you have to rename
> such-and-such... yes, I know that file already exists..."

    +0. Maybe copy them so that there's always an unmodified "fallback" copy

    Martin
-- 
| S I E M E N S |  <Ma...@mch.sni.de>  |      Siemens Nixdorf
| ------------- |   Voice: +49-89-636-46021     |  Informationssysteme AG
| N I X D O R F |   FAX:   +49-89-636-44994     |   81730 Munich, Germany
~~~~~~~~~~~~~~~~My opinions only, of course; pgp key available on request

Re: Some Win32 release stuff....

Posted by Paul Sutton <pa...@c2.net>.
On Tue, 19 May 1998, Brian Behlendorf wrote:
> 1) could we change access_log and error_log to access.log and error.log in the
> .conf-dist-win files?

+1

> 2) can we change the .conf-dist-win files to simply be .conf files when the
> Win32 release gets built?  it avoids the clunky "first you have to rename
> such-and-such... yes, I know that file already exists..."

Umm, the binary installer now emulates pretty closely what APACI's make
install does (since consistency is good). That is: the configuration files
are installed as

  conf\httpd.conf.default,
  conf\mime.types.default
  ...

Then, for each file, if the corresponding file without ".default" _does
not exist_, it is _copied_ to the final filename. So that a new
installation ends with a conf directory containing all the "live" files,
plus the ".default" ones. But on an upgrade no existing files are
overwritten, and the user has "*.default" files in the conf directory to
compare against their live files and upgrade bits as needed.

Similarly for the htdocs directory, where htdocs\index.html is
not overwriten if it does not exist (in this case, index.html.default is
not used). The main difference from APACI is that the windows installer
always installs the manuals (into htdocs\manuals) [provided the user
selects the manuals component, of course] even if the htdocs directory
exists. In APACI if htdocs exists, htdocs/manuals is not installed (which
may be a mistake, since it leaves the user with an outdated
htdocs/manuals).

However I would much prefer to see us install the manuals into a top-level
manuals directory, and add "Alias /manuals @@ServerRoot@@/manuals" to
httpd.conf. They we could always safely upgrade the user's manuals without
touching their document root.

Paul