Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CEDBAC5.8060209@ece.gatech.edu> Date: Fri, 24 May 2002 00:00:05 -0400 From: Charles Wilson 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: cygwin-apps AT cygwin DOT com Subject: Re: libpng dependencies References: <3CEDB857 DOT 7070208 AT ece DOT gatech DOT edu> <20020524035505 DOT GB8819 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > You know, I could modify upset so that you could do something like: > > requires: cygwin1.dll cygpng10.dll > > without too much effort. as opposed to 'libpng10' (the package which contains cygpng10.dll)? Mebbe. I know that rpm auto-computes that kind of dependency. But in the case of libpngX, it's a one-to-one mapping. For other packages, where package 'bar' contains 'cygbar.dll' and some import libs and some executables and some headers, it might be helpful. I dunno. It's up to the people who *depend on* libpng. As for my packages, when I write the requires: line, I just check what package contains the dlls I need and put it in. Oh, but your version would auto-update the dependency (so that the correct *package* is chosen) based on where the dll is. In case some tomfool library maintainer goes and restructures his packages. Ummmm, nobody here but us mice... > > Would this be worthwhile? Yes, given the auto-correcting behavior it would bestow. --Chuck