Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
X-Apparently-From: <earnie?boyd AT yahoo DOT com>
Message-ID: <3B13AE87.11095F1D@yahoo.com>
Date: Tue, 29 May 2001 10:13:27 -0400
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: Cygwin Users <cygwin AT cygwin DOT com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: bkeener AT thesoftwaresource DOT com, cygwin AT cygwin DOT com
Subject: Re: Setup.exe v2.56
References: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F016 AT itdomain002 DOT itdomain DOT net DOT au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Robert Collins wrote:
> 
> > -----Original Message-----
> > From: Brian Keener [mailto:bkeener AT thesoftwaresource DOT com]
> > Sent: Monday, May 28, 2001 2:00 PM
> > To: cygwin AT cygwin DOT 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'.
> 

No, it was an intentional benefit as designed by DJ and was advertised
on this list as such.

> > > 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.
> 

Hmm...  However, if a setup.ini doesn't exist then setup should still
work as it did in previously which was to install any .tar.gz file in
the directory and sub-directories recursively that setup.exe resides in.

> 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).
> 

Maybe a good idea but still the method described above needs to be dealt
with.

-- 
Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple