You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Marc Slemko <ma...@worldgate.com> on 1998/07/14 22:14:41 UTC
who has is2 they can use
Ben, can you verify if you really can build the single file install?
Re: who has is2 they can use
Posted by Ben Hyde <bh...@pobox.com>.
Ben Laurie writes:
> ... the existing apache.iwz file is somewhat eccentric,
"The amazing thing is not how well the bear can
dance but that he dances at all." - ben hyde
Re: who has is2 they can use
Posted by Ben Laurie <be...@algroup.co.uk>.
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/
Re: who has is2 they can use
Posted by Paul Sutton <pa...@ukweb.com>.
On Sun, 19 Jul 1998, Rodent of Unusual Size wrote:
> Paul Sutton wrote:
> > 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.
>
> I'm only following this peripherally at the moment, but that 'extract
> it into the build directory, copy it into the build directory' sounds
> very surreal to me.
Yeah, well, a lot of pointless things happen on NT systems.
"Extract into the XXX directory, then copy into the YYY directory, where
XXX and YYY can be either of "install" or "build" as long as XXX and YYY
are different."
Paul
Re: who has is2 they can use
Posted by Rodent of Unusual Size <Ke...@Golux.Com>.
Paul Sutton wrote:
>
> 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.
I'm only following this peripherally at the moment, but that 'extract
it into the build directory, copy it into the build directory' sounds
very surreal to me.
#ken P-)}
Ken Coar <http://Web.Golux.Com/coar/>
Apache Group member <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>
Re: who has is2 they can use
Posted by Paul Sutton <pa...@awe.com>.
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).
Paul
Re: who has is2 they can use
Posted by Ben Laurie <be...@algroup.co.uk>.
Paul Sutton wrote:
>
> On Fri, 17 Jul 1998, Ben Laurie wrote:
> > Paul Sutton wrote:
> > > It's designed so you only have to do a single search-and-replace to get
> > > your local paths into it, but it is certainly easier if you do an Apache
> > > build and install to the default location (C:\Apache), since then
> > > apache.iwz doesn't need changing.
> >
> > Errr ... right - so MSVCRT.DLL lives in the Apache install directory,
> > does it? (For example).
>
> Yes. IS2's configuration has to pick it up from somewhere. On most systems
> that would be C:\WINNT\SYSTEM32 or C:\WINDOWS or whereever, but that is
> system dependent, meaning you would *definitely* have to customise
> apache.iwz for your site. Or you might keep your MSVC redistributable
> files somewhere separate from the live windows directories.
>
> Instead, the how-to-build docs tell you to copy MSVCRT.DLL from whereever
> you prefer to keep it into C:\Apache, so that it is in a known location
> for apache.iwz. There's even a copy of cut-n-paste commands in the
> how-to-release doc for windows and windows NT systems to make this
> trivially easy (assuming I committed that -- I think I did).
>
> Similarly for the source, conf and other directories. You might check them
> out anywhere, but as long as you follow the docs and copy them to
> C:\Apache (or whereever) everything is reduced to a dependency on a single
> path.
>
> > Put it this way - I did do a build and install to the default location,
> > and apache.iwz needed LOADS of changing.
>
> I still don't understand why. Are you following the how-to-release?
Errr, nope. It'll work much better if I do!
> What
> needed changing? What files are not in the right place in C:\Apache? I
> think there may be one or two differences from 1.3.0 to 1.3.1 but nothing
> serious.
Yeah, seems that way.
> > I suspect you are assuming that c:\apache is also where the CVS tree
> > lives, which ain't the case in this part of the world. And doesn't
> > explain msvcrt.
>
> 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.
> 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?
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/
Re: who has is2 they can use
Posted by Paul Sutton <pa...@awe.com>.
On Fri, 17 Jul 1998, Ben Laurie wrote:
> Paul Sutton wrote:
> > It's designed so you only have to do a single search-and-replace to get
> > your local paths into it, but it is certainly easier if you do an Apache
> > build and install to the default location (C:\Apache), since then
> > apache.iwz doesn't need changing.
>
> Errr ... right - so MSVCRT.DLL lives in the Apache install directory,
> does it? (For example).
Yes. IS2's configuration has to pick it up from somewhere. On most systems
that would be C:\WINNT\SYSTEM32 or C:\WINDOWS or whereever, but that is
system dependent, meaning you would *definitely* have to customise
apache.iwz for your site. Or you might keep your MSVC redistributable
files somewhere separate from the live windows directories.
Instead, the how-to-build docs tell you to copy MSVCRT.DLL from whereever
you prefer to keep it into C:\Apache, so that it is in a known location
for apache.iwz. There's even a copy of cut-n-paste commands in the
how-to-release doc for windows and windows NT systems to make this
trivially easy (assuming I committed that -- I think I did).
Similarly for the source, conf and other directories. You might check them
out anywhere, but as long as you follow the docs and copy them to
C:\Apache (or whereever) everything is reduced to a dependency on a single
path.
> Put it this way - I did do a build and install to the default location,
> and apache.iwz needed LOADS of changing.
I still don't understand why. Are you following the how-to-release? What
needed changing? What files are not in the right place in C:\Apache? I
think there may be one or two differences from 1.3.0 to 1.3.1 but nothing
serious.
> I suspect you are assuming that c:\apache is also where the CVS tree
> lives, which ain't the case in this part of the world. And doesn't
> explain msvcrt.
No, C:\Apache is just an intermediate directory. You should not check out
apache into it, 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.
Paul
Re: who has is2 they can use
Posted by Marc Slemko <ma...@worldgate.com>.
On Fri, 17 Jul 1998, Ben Laurie wrote:
> Paul Sutton wrote:
> >
> > On Wed, 15 Jul 1998, Ben Laurie wrote:
> > > Marc Slemko wrote:
> > > > Ben, can you verify if you really can build the single file install?
> > >
> > > Yes, I can, though the existing apache.iwz file is somewhat eccentric,
> > > so I have to change a lot of paths, but at the end of the day, I get a
> > > single file install, yes.
> >
> > It's designed so you only have to do a single search-and-replace to get
> > your local paths into it, but it is certainly easier if you do an Apache
> > build and install to the default location (C:\Apache), since then
> > apache.iwz doesn't need changing.
>
> Errr ... right - so MSVCRT.DLL lives in the Apache install directory,
> does it? (For example).
Yes, if you follow the step by step instructions posted on dev.apache.org.
If someone wishes to update the file to have the current set of files
required, etc. that would be useful to do now, before 1.3.1 is tagged.
>
> Put it this way - I did do a build and install to the default location,
> and apache.iwz needed LOADS of changing.
>
> I suspect you are assuming that c:\apache is also where the CVS tree
> lives, which ain't the case in this part of the world. And doesn't
That may be so, but we need to pick some path. Personally, I would prefer
some completely seperate path (eg. c:\apacherawcvscraptoinstalljunk).
> explain msvcrt.
>
> 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/
>
Re: who has is2 they can use
Posted by Ben Laurie <be...@algroup.co.uk>.
Paul Sutton wrote:
>
> On Wed, 15 Jul 1998, Ben Laurie wrote:
> > Marc Slemko wrote:
> > > Ben, can you verify if you really can build the single file install?
> >
> > Yes, I can, though the existing apache.iwz file is somewhat eccentric,
> > so I have to change a lot of paths, but at the end of the day, I get a
> > single file install, yes.
>
> It's designed so you only have to do a single search-and-replace to get
> your local paths into it, but it is certainly easier if you do an Apache
> build and install to the default location (C:\Apache), since then
> apache.iwz doesn't need changing.
Errr ... right - so MSVCRT.DLL lives in the Apache install directory,
does it? (For example).
Put it this way - I did do a build and install to the default location,
and apache.iwz needed LOADS of changing.
I suspect you are assuming that c:\apache is also where the CVS tree
lives, which ain't the case in this part of the world. And doesn't
explain msvcrt.
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/
Re: who has is2 they can use
Posted by Paul Sutton <pa...@c2.net>.
On Wed, 15 Jul 1998, Ben Laurie wrote:
> Marc Slemko wrote:
> > Ben, can you verify if you really can build the single file install?
>
> Yes, I can, though the existing apache.iwz file is somewhat eccentric,
> so I have to change a lot of paths, but at the end of the day, I get a
> single file install, yes.
It's designed so you only have to do a single search-and-replace to get
your local paths into it, but it is certainly easier if you do an Apache
build and install to the default location (C:\Apache), since then
apache.iwz doesn't need changing.
Paul
Re: who has is2 they can use
Posted by Ben Laurie <be...@algroup.co.uk>.
Brian Behlendorf wrote:
>
> At 03:44 PM 7/15/98 -0600, Marc Slemko wrote:
> >On Wed, 15 Jul 1998, Ben Laurie wrote:
> >
> >> > > so I have to change a lot of paths, but at the end of the day, I get a
> >> > > single file install, yes.
> >>
> >> BTW, did someone blow away CHANGES in the top directory?
> >
> >Yes. Brian I think.
>
> Yes, because it was completely redundant, not really a "CHANGES" file but
> more of a "new features" file, and a pain to keep in sync with the other
> places we talk about new features.
No problem - just doing a reality check.
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/
Re: who has is2 they can use
Posted by Brian Behlendorf <br...@hyperreal.org>.
At 03:44 PM 7/15/98 -0600, Marc Slemko wrote:
>On Wed, 15 Jul 1998, Ben Laurie wrote:
>
>> > > so I have to change a lot of paths, but at the end of the day, I get a
>> > > single file install, yes.
>>
>> BTW, did someone blow away CHANGES in the top directory?
>
>Yes. Brian I think.
Yes, because it was completely redundant, not really a "CHANGES" file but
more of a "new features" file, and a pain to keep in sync with the other
places we talk about new features.
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
pure chewing satisfaction brian@apache.org
brian@hyperreal.org
Re: who has is2 they can use
Posted by Marc Slemko <ma...@worldgate.com>.
As long as there are no 8.3 problems.
No, there shouldn't be.
On Thu, 16 Jul 1998, Brian Behlendorf wrote:
> At 09:25 AM 7/16/98 +0000, Paul Sutton wrote:
> >On Wed, 15 Jul 1998, Ben Laurie wrote:
> >> +1. There's already a README.NT in the top dir. Add it there?
> >
> >Oh, that reminds me, there is a problem with README.NT. When
> >IS2 comes to display it at the end it uses the associations from the
> >registry to know what viewer to launch, and NT isn't a known extension so
> >it doesn't display it. So README.NT needs renaming to README.TXT before
> >running the IS2 build process, and update the corresponding option in IS2
> >from README.NT to README.TXT.
>
> Or, "README-NT.TXT". :)
>
> Brian
>
>
> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
> "Common sense is the collection of prejudices | brian@apache.org
> acquired by the age of eighteen." - Einstein | brian@hyperreal.org
>
Re: who has is2 they can use
Posted by Brian Behlendorf <br...@hyperreal.org>.
At 09:25 AM 7/16/98 +0000, Paul Sutton wrote:
>On Wed, 15 Jul 1998, Ben Laurie wrote:
>> +1. There's already a README.NT in the top dir. Add it there?
>
>Oh, that reminds me, there is a problem with README.NT. When
>IS2 comes to display it at the end it uses the associations from the
>registry to know what viewer to launch, and NT isn't a known extension so
>it doesn't display it. So README.NT needs renaming to README.TXT before
>running the IS2 build process, and update the corresponding option in IS2
>from README.NT to README.TXT.
Or, "README-NT.TXT". :)
Brian
--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
"Common sense is the collection of prejudices | brian@apache.org
acquired by the age of eighteen." - Einstein | brian@hyperreal.org
Re: who has is2 they can use
Posted by Paul Sutton <pa...@c2.net>.
On Wed, 15 Jul 1998, Marc Slemko wrote:
> There could be a mess of files that have to be updated for the installer.
> Also note that I dislike the current way of not including the full source
> tree; on Unix we include the win32 directory, so why not include the unix
> directory, etc. on win32?
Yes I don't care either way, but it seems a bit redundant on Windows
systems to include Unix specific files and directories. It is also an easy
way of keeping the archive size down a bit. The problem is keeping all the
directories up to date in IS2. You have an manually go through every
directory, comparing it against the files in the new release and
adding/remove files as needed. This takes long enough with the current
set of directories... adding more will make this even more of a pain to
do.
Paul
Re: who has is2 they can use
Posted by Marc Slemko <ma...@worldgate.com>.
On Wed, 15 Jul 1998, Ben Laurie wrote:
> > > so I have to change a lot of paths, but at the end of the day, I get a
> > > single file install, yes.
>
> BTW, did someone blow away CHANGES in the top directory?
Yes. Brian I think.
There could be a mess of files that have to be updated for the installer.
Also note that I dislike the current way of not including the full source
tree; on Unix we include the win32 directory, so why not include the unix
directory, etc. on win32?
>
> > Cool.
> >
> > Oh, I think we should add a "readme" to the install process saying
> > something like:
> >
> > WARNING: The Win32 release of Apache should still be considered beta
> > quality code. It does not meet the normal standards of stability and
> > security that Unix releases do. There are numerous known bugs and
> > inconsistencies. There is also a much greater chance of security holes
> > being present in the Win32 version of Apache.
>
> +1. There's already a README.NT in the top dir. Add it there?
>
Sure, but whatever you do it has to pop up when they install it so that
they see it without scrolling anything or saying "yes, show me the
readme".
Re: who has is2 they can use
Posted by Ask Bjoern Hansen <as...@netcetera.dk>.
On Wed, 15 Jul 1998, Ben Laurie wrote:
> +1. There's already a README.NT in the top dir. Add it there?
shouldn't this file be called README.win32 or something like that?
ask
---------------------------------------------------------------------
ask bjoern hansen - Netcetera - Finsensvej 80 - DK-2000 Frederiksberg
tlf 38 88 32 22 / 40 44 58 66 / 38 88 20 38 ext 341 - Fax 38 88 30 38
Webdesign, Webhotel, Mailhotel, UUCP & more! http://www.netcetera.dk/
Re: who has is2 they can use
Posted by Paul Sutton <pa...@c2.net>.
On Wed, 15 Jul 1998, Ben Laurie wrote:
> +1. There's already a README.NT in the top dir. Add it there?
Oh, that reminds me, there is a problem with README.NT. When
IS2 comes to display it at the end it uses the associations from the
registry to know what viewer to launch, and NT isn't a known extension so
it doesn't display it. So README.NT needs renaming to README.TXT before
running the IS2 build process, and update the corresponding option in IS2
from README.NT to README.TXT.
Paul
Re: who has is2 they can use
Posted by Ben Laurie <be...@algroup.co.uk>.
Marc Slemko wrote:
>
> On Wed, 15 Jul 1998, Ben Laurie wrote:
>
> > Marc Slemko wrote:
> > >
> > > Ben, can you verify if you really can build the single file install?
> >
> > Yes, I can, though the existing apache.iwz file is somewhat eccentric,
>
> Eccentric is one word for it.
I did try to restrain myself :-)
> > so I have to change a lot of paths, but at the end of the day, I get a
> > single file install, yes.
BTW, did someone blow away CHANGES in the top directory?
> Cool.
>
> Oh, I think we should add a "readme" to the install process saying
> something like:
>
> WARNING: The Win32 release of Apache should still be considered beta
> quality code. It does not meet the normal standards of stability and
> security that Unix releases do. There are numerous known bugs and
> inconsistencies. There is also a much greater chance of security holes
> being present in the Win32 version of Apache.
+1. There's already a README.NT in the top dir. Add it there?
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/
Re: who has is2 they can use
Posted by Marc Slemko <ma...@worldgate.com>.
On Wed, 15 Jul 1998, Ben Laurie wrote:
> Marc Slemko wrote:
> >
> > Ben, can you verify if you really can build the single file install?
>
> Yes, I can, though the existing apache.iwz file is somewhat eccentric,
Eccentric is one word for it.
> so I have to change a lot of paths, but at the end of the day, I get a
> single file install, yes.
Cool.
Oh, I think we should add a "readme" to the install process saying
something like:
WARNING: The Win32 release of Apache should still be considered beta
quality code. It does not meet the normal standards of stability and
security that Unix releases do. There are numerous known bugs and
inconsistencies. There is also a much greater chance of security holes
being present in the Win32 version of Apache.
Re: who has is2 they can use
Posted by Ben Laurie <be...@algroup.co.uk>.
Marc Slemko wrote:
>
> Ben, can you verify if you really can build the single file install?
Yes, I can, though the existing apache.iwz file is somewhat eccentric,
so I have to change a lot of paths, but at the end of the day, I get a
single file install, yes.
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/
Re: who has is2 they can use
Posted by Marc Slemko <ma...@worldgate.com>.
Anyone?
Can anyone build a win32 build with a single file is2 install within 24
hours of the tarball being rolled?
On Tue, 14 Jul 1998, Marc Slemko wrote:
> Ben, can you verify if you really can build the single file install?
>