Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Subject: RE: Setup.exe v2.56 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 28 May 2001 14:05:43 +1000 Message-ID: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Setup.exe v2.56 Thread-Index: AcDnKp7zQQITyu1DTs+l6xSrugnVzwAAGDCg From: "Robert Collins" To: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id AAA07244 > -----Original Message----- > From: Brian Keener [mailto:bkeener@thesoftwaresource.com] > Sent: Monday, May 28, 2001 2:00 PM > To: cygwin@cygwin.com > Subject: Re: Setup.exe v2.56 > > > Travis Howell wrote: > > The last released Cygwin setup version (2.29) works fine without sub > > directories or setup.ini. I suspect that was an unintentional 'benefit'. > > But won't that changes be overwriten each time setup.ini is > updated on Cygwn > > FTP sites ? > > Each time you do a Download from Internet or an Install from > Internet - yes. More of a problem is that once setup understands dependencies, a setup.ini will be mandatory. The directory structure is really moot vs the need for setup to have accurate metainformation. IMO Travis, your best bet is to create a patch to the current setup.exe that reads an additional file - local.packages or some such, which lists your additional packages that you want installed, and adds them to the list of available packages. Such a change would be fairly unobtrusive, seem to give you your key requirements (installation of additional files over the "official" packages). Rob -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple