httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Laurie <...@algroup.co.uk>
Subject Re: who has is2 they can use
Date Sat, 18 Jul 1998 21:16:22 GMT
Paul Sutton wrote:
> 
> On Sat, 18 Jul 1998, Ben Laurie wrote:
> > Paul Sutton wrote:
> > > No, C:\Apache is just an intermediate directory. You should not check out
> > > apache into it,
> >
> > Hmmm ... I quote "Now create the install directory, and extract Apache
> > into it. The Apache files will normally come either direct from CVS at a
> > given tag value, or ...". That sounds rather liking checking apache out
> > to me.
> 
> Well, you need to ensure that the src, conf, etc directories get into the
> install directory. In practise what happens is you grab the Unix release
> tar.gz, extract it into the build directory, copy it into the build
> directory, build it, install it into the install directory. So the install
> directory ends up with the correct distribution files (i.e. after the unix
> how-to-release process has been followed) with the installed Win32 files
> overlaid onto that directory structure.
> 
> I guess you could checkout direct into the install directory but you would
> end up with some files and directories you shouldn't have in the install
> tree (for example, STATUS, CVS, .cvsignore). If you follow the Unix
> how-to-release first you should be ok.
> 
> Note of course the IS2 only builds files listed in its config, so these
> extra files would be ignored, but if you use drag-n-drop to update the IS2
> config to the current set of files you'd end up with undesirable files in
> the configuration.
> 
> Probably the docs should either explain all this, or just remove the
> reference to CVS checkout. That might be easier.
> 
> > > nor build Apache in it. This is should be documented.  It
> > > could be anything (as the documentation explains) if you already have a
> > > C:\Apache. You should make sure that C:\Apache (or whatever intermediate
> > > directory you use) is completely empty before starting a build.
> >
> > That's a pain, then I have to check it out twice! Is this really
> > necessary? Can't I just check out Apache to c:\apache then build/install
> > it, then run IS2?
> 
> No, check it out once and copy it locally! You could build/install it all
> in C:\Apache I guess, but as above you then couldn't update the IS2 config
> easily by drag-n-drop (not that that is easy since you have to do it for
> every directory and you have to use the annoying GUI).

Sigh. Can't we just use a self-extracting zip?

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/

WE'RE RECRUITING! http://www.aldigital.co.uk/recruit/

Mime
View raw message