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: <00af01c0b3f0$e751e200$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "DJ Delorie" <dj AT delorie DOT com>, <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>
Subject: Re: setup revisit
Date: Sat, 24 Mar 2001 10:28:00 +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: 23 Mar 2001 23:22:23.0571 (UTC) FILETIME=[1D8D8230:01C0B3F0]

----- Original Message -----
From: "DJ Delorie" <dj AT delorie DOT com>
To: <cygwin-developers AT cygwin DOT com>
Sent: Saturday, March 24, 2001 9:58 AM
Subject: Re: setup revisit


>
> > When DJ rewrote setup.exe he opted not go go this route.  Maybe he
can
> > reiterate his reasons for doing this.
>
> It was way bigger than it needed to be.  It was likely to become
> instantly obsolete.  It was often incompatible with already-loaded
> DLLs. There were GPL issues.
>

I'm against the idea of building "intelligence" into setup.exe (making
it the 33rd packaging and distribution format).
So, the question becomes (for me :] ) how much effort will be required
to port rpmfind and rpm to win32, as statically linked libraries that
setup.exe can use. Ah, just had an insight into the GPL issues - which
if I guess right means that I cannot port and use rpmfind??

What GPL issues am I going to run into? The Redhat need to dual licence
the resulting tool? Howabout I leave the existing setup alone, except
for the ability to do a bootstrap IFF it's built with a given #define?
Then all the bootstrap code goes in a different directory, and is GPL
only licenced. My idea being that your commercial customers who are
getting a minimal fixed set install _anyway_ don't need and won't
appreciate flexible package and dependency tools.

<soapbox>

In summary, if for a given route the GPL issues mean I cannot leverage
an existing packaging & distro format, I'm not interested in taking that
route. I'm happy to contribute code _I've written_ to redhat, so that
the cygwin I use gets better. I'm just not interested in finding new
solutions to already solved problems. I am interested in getting an
existing solution onto win32 via porting however.
</soapbox>

Why instantly obsolete? 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. How often does the rpm format change
(ok trick question :] rpm is rather volatile). More important question:
if I take the ported rpm 3, and use the patchs to port rpm 4, then we
can sit there without headaches...

As far as size goes, I can look into ways to make that the bootstrap
smaller - I've got some thoughts there. It's going to be a lot smaller
than a linux bootstrap environment :]

Rob