Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: RFC: setup.ini change
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Date: Wed, 1 May 2002 23:51:10 +1000
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5F73@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g41DpFY28492



> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Wednesday, May 01, 2002 2:43 AM

> >Chris, can we get that "external-src: other-pkg-name" thing 
> into upset? 
> >   (or "other-src" or whatever) Reminder:
> 
> It's pretty complicated to add.  If you specify external-src 
> it will potentially have to add test, prev, curr entries for 
> the packages.
> 
> However, IMO, it makes sense for this option to actually be 
> passed into setup.ini so that setup.exe can understand that 
> this is basically a symbolic link rather than a "copy".

Setup doesn't need any changes - the
source: 
tag has all the functionality Chuck needs now. It'll only download the
file once (well, there are some corner cases, but relatively few and far
between).
 
> I don't remember if Robert already indicated which method 
> he'd prefer. Maybe he already has plans to do the right thing 
> when multiple packages refer to the same source tar ball.  I 
> seem to recall that this came up before but I don't remember 
> what the decision was.

I think that the easiest way is to allow setup.hint: to include the
literal source: tag.

As far as setup.ini's lex and yacc rules, any valid path is ok, so there
is no need to consider adding a new tag.

Rob