Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Fri, 23 Mar 2001 20:57:47 -0500 Message-Id: <200103240157.UAA04918@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: robert DOT collins AT itdomain DOT com DOT au CC: cygwin-developers AT cygwin DOT com In-reply-to: <02da01c0b404$edd91670$0200a8c0@lifelesswks> (robert DOT collins AT itdomain DOT com DOT au) Subject: Re: setup revisit 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> > 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. > 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.