Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Message-ID: <3C05FD7E.2090708@ece.gatech.edu>
Date: Thu, 29 Nov 2001 04:18:54 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: cygwin AT cygwin DOT com, cygwin-apps AT sources DOT redhat DOT com
Subject: Re: setup current problems
References: <009401c178b4$0d3d92b0$0200a8c0 AT lifelesswks> <3C05FB2F DOT 2050409 AT ece DOT gatech DOT edu> <00af01c178b5$aa39e860$0200a8c0 AT lifelesswks>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Robert Collins wrote:

> 
> Yes, which is why I'm fixing setup, not hammering on your door about
> setup.ini :}.

Okay, well while you're mucking with the setup code, I've got a question 
for you:

1) joe user has the autoconf package installed on his system.  in the 
past, autoconf depended only on cygwin, perl, m4

2) now, the new version of autoconf depends on cygwin, perl, m4, AND 
autoconf-devel + autoconf-stable.  (I KNOW that joe user doesn't have 
autoconf-devel/stable installed because they are brand new packages)

Q: will setup automatically select autoconf-devel and autoconf-stable if 
joe chooses to update his autoconf to the new version?  Why?  (merely 
because -stable and -devel are NEW, or because of the new dependency 
specified by setup.ini for autoconf itself?)

Q: what if the new dependency was on a package -- say, 'squid' -- that 
has been around a long time, and joe has previously skipped (so now it's 
"permanently" skipped).  Will setup present 'squid' as a new required 
dependency and automatically select it if joe decides to update his 
existing autoconf?

--Chuck


--Chuck