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: <02e901c0b406$561787c0$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "DJ Delorie" <dj AT delorie DOT com>
Cc: <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> <200103240142 DOT UAA04756 AT envy DOT delorie DOT com> <02da01c0b404$edd91670$0200a8c0 AT lifelesswks> <200103240157 DOT UAA04918 AT envy DOT delorie DOT com>
Subject: Re: setup revisit
Date: Sat, 24 Mar 2001 13:01:25 +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:55:48.0778 (UTC) FILETIME=[8C48A0A0:01C0B405]

----- Original Message -----
From: "DJ Delorie" <dj AT delorie DOT com>
To: <robert DOT collins AT itdomain DOT com DOT au>
Cc: <cygwin-developers AT cygwin DOT com>
Sent: Saturday, March 24, 2001 12:57 PM
Subject: Re: setup revisit


>
> > Thus I'm willing to try and build rpm into a library linked into
> > setup.exe
>
> That would be fine.  It's OK to have setup support other package
> formats, as long as the user doesn't need to know that it's doing
> that.  But even RPM has a master file similar to setup.ini.
>
> > Ah. So if we use the same source, there's no issue.
>
> Easier said than done.  One problem with the original setup is that
> the tar and gzip (and cygwin) packages got updated occasionally, and
> every time that happened, someone had to remember to rebuild setup.

Easier done than said in this case. I'm proposing that the current
setup.__ini__ be stripped to only include the bootstrap files. So
setup.exe *never* gets rebuilt (for those reasons). It is data driven.
I've got no issues with the layout or approach setup.exe has taken -
just the replication of effort. This covers the issue for RPM's master
file concept as well - setup.ini includes a pointer to the RPM database
(which gets mirrored).

>
> > Sorry for my shorthand - "the link to" should be prefixed by "in a
> > bootstrap environment ".
>
> One problem with the original setup is that it didn't include the
> source trees.  The developer had to have the binaries installed, and
> the Makefile pulled them from your bin directory.  That made keeping
> track of the right sources even harder.
>

I've just seen Chris' response.. that does seem rather complex. I think
I'm taking a much simpler approach.

Rob