Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "'Charles Wilson'" <cwilson AT ece DOT gatech DOT edu>,
   "'Jan Nieuwenhuizen'" <janneke AT gnu DOT org>
Cc: <cygwin AT cygwin DOT com>
Subject: RE: missing file FOO.dll
Date: Sat, 1 Jun 2002 02:03:53 +1000
Message-ID: <000701c208bc$c3346560$0200a8c0@lifelesswks>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <3CF78EB7.8080506@ece.gatech.edu>
X-OriginalArrivalTime: 31 May 2002 16:03:53.0900 (UTC) FILETIME=[C30BCEC0:01C208BC]



> -----Original Message-----
> From: Chuck...

> [mailto:cygwin-owner AT cygwin DOT com] On Behalf Of Charles Wilson
> Worse, assume that I had previously installed the official cygwin 
> package of ghostscript.  Even if Dario has updated his 
> setup.hint to now 
> require the libpng2 package, I won't pick up that changed dependency 

Setup should deal with this correctly today. When adding ghostscript to
the chooser it will use the current setup.ini's requires: list, not the
old one.

> I mean, we could have setup do the following:
>    1) look at all currently installed packages
>    2) check the requires: line of the corresponding packages in the 
> just-downloaded setup.ini
>    3) if any requirements for currently installed packages 
> are missing, 
> add those (new) requirements to the default "to be installed" list.

Yup. AFAIK, that's what it does now. 
 
> But, that's silly: what if MY installed version of 'foo' does NOT 
> require 'bar', but the current version of 'foo' DOES rquire 
> it?  I don't 
> *need* to install 'bar' unless I install the new 'foo'.  

Weeel. Yes. And per version meta data will sort that out. As it stands
though, setup will assume that you want to update foo, and therefore
pickup on bar as well. If the version number hasn't changed, then
installing bar is the correct thing, as it is a missing dependency (even
if it's a new package resulting from a package split.


> We could have per-version requirements: in setup.hint...but then we 
> still need to add the three steps outlined above to setup's algorithm.

And more. We need more work on the local database before per-version
requirements are really useful.
 
> As I explained, XEmacs doesn't HAVE a setup.hint.

XEmacs uses a fork of setup. Someone who cares might like to suggest
that they update their fork to a more recent codebase, or ... provide a
setup.ini for cygwin users.
 
Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/