Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Message-ID: <02ec01c0b406$6e3822b0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
References: <009201c0b373$270a6ee0$0200a8c0 AT lifelesswks> <20010323174032 DOT A30954 AT redhat DOT com> <200103232258 DOT RAA03576 AT envy DOT delorie DOT com> <00af01c0b3f0$e751e200$0200a8c0 AT lifelesswks> <200103232349 DOT SAA03971 AT envy DOT delorie DOT com> <021801c0b3fb$97ff2d60$0200a8c0 AT lifelesswks> <20010323204621 DOT B17066 AT redhat DOT com>
Subject: Re: setup revisit
Date: Sat, 24 Mar 2001 13:02:05 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 24 Mar 2001 01:56:30.0107 (UTC) FILETIME=[A4EAEEB0:01C0B405]

----- Original Message -----
From: "Christopher Faylor" <cgf AT redhat DOT com>
To: <cygwin-developers AT cygwin DOT com>
Sent: Saturday, March 24, 2001 12:46 PM
Subject: Re: setup revisit


> On Sat, Mar 24, 2001 at 11:44:27AM +1100, Robert Collins wrote:
> >> > If the bootstrap is a separate tarball that it checks for (like
it
> >> > does setup.ini), then the core engine is going to stay the same
for
> >> > a looong time.
> >>
> >> If the bootstrap is a tarball, you need tar and gzip outside that
> >> anyway.  If you have that, why not just use it to install *all* the
> >> tarballs?
> >
> >Because
> >a) you cannot add (for example) bzip2 without changing setup -
porting
> >bzip2 to raw win32
>
> I know that you are just giving an example but porting to use bz2
would
> be pretty trivial these days.

Uhmm, trivial without cygwin1.dll ? I presume thanks to the work at the
mingw project.. Next example: rpm (depends on sleepycat db (raw win32
only builds in MSVC at the moment) and possibly perl.

If you meant porting bz2 with cygwin1.dll, well that's the whole point:]

> >Cool. I believe I can keep the overhead within 20% of the original -
by
> >splitting out the bootstrap tarball and using the separate files as
part
> >of the download cache.
>
> You still have cygwin conflict issues.  We used to have to say "Stop
all
> Cygwin programs" but, surprise, people didn't do this and were
confused
> on the mailing list.

Actually you *still* have to say that. I get caught by cygipc.exe on a
routine basis - and I hope I'm not your average newbie. You will
*always* have to say that until whatever is trying to replace
cygwin1.dll / bash to name the most probable culprits is able to do
"behind the scenes" work. See my comments re replaceing files on reboot
for a long term solution.

> At any rate, this sounds like a long-term goal for setup.exe not a
short
> term one.  I was hoping that someone could add some simple dependency
> analysis to setup.exe and come up with some way of grouping things
> by category.  That should be relatively simple compared to redoing the
> entire installation to use apt or rpm.
>
> cgf
>

True. I was hoping to put my nose down and hack all weekend, but it
looks like rpm is *not* going to play nice so I'll give it a slightly
lower priority for now.

Rob