From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19019 invoked by alias); 20 Aug 2008 19:23:15 -0000 Received: (qmail 19009 invoked by uid 22791); 20 Aug 2008 19:23:14 -0000 X-Spam-Check-By: sourceware.org Received: from out3.smtp.messagingengine.com (HELO out3.smtp.messagingengine.com) (66.111.4.27) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 20 Aug 2008 19:22:36 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 22B9615B025 for ; Wed, 20 Aug 2008 15:22:34 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 20 Aug 2008 15:22:34 -0400 Received: from [192.168.1.3] (user-0c6suln.cable.mindspring.com [24.110.122.183]) by mail.messagingengine.com (Postfix) with ESMTPSA id 6EC291DFE; Wed, 20 Aug 2008 15:22:33 -0400 (EDT) Message-ID: <48AC6EF7.80302@cwilson.fastmail.fm> Date: Wed, 20 Aug 2008 19:23:00 -0000 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.16) Gecko/20080708 Thunderbird/2.0.0.16 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Mailing List: CygWin-Apps Subject: Re: accumulated upset warnings: clisp, gnome, ImageMagick, libtool, clamav, gnutls, guile, jasper, tetex, guile References: <20080820043427.GA7616@ednor.casa.cgf.cx> <20080820155630.GA9366@ednor.casa.cgf.cx> <48AC4944.1080506@cwilson.fastmail.fm> <20080820173026.GA9685@ednor.casa.cgf.cx> In-Reply-To: <20080820173026.GA9685@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-08/txt/msg00200.txt.bz2 Christopher Faylor wrote: > I explained this in the first message of this thread. For > external-source, upset only knows about files that would show up in > setup.ini: > > % grep libtool-1.5.25a-1-src setup.ini > % Now I get what is different about libtool, and every other "library" package I've ever managed through multiple releases. Usually, the "old" lib*N/ directories contain exactly one binary file, and a copy-and-renamed-version of the appropriate -src package. the "current" lib*N directory contains some number x binary packages. The top-level directory contains the same number x -src packages. If x > 3, that's ok: because the 4,5,6... versions of the "old" lib*N package don't show up in setup.ini either -- so it doesn't matter that their corresponding -src packages don't show up in that file. However, in the case of libtool, I (was) trying to keep both libltdl3/ and libltdl7/ "active". Which means libltdl3/ might have 2 or 3 entries -- all of which appear in setup.ini. AND libltdl7 might have 2 or 3 entries which all appear in setup.ini. But that means I'd need 4 or 6 version of the libtool*-src package in setup.ini. Bang, you're dead. Well, it's water under the bridge now: I'm pretty happy with libtool-2.2.x. I think after the upcoming 2.2.6 release I'll officially stop supporting libtool-1.5.x, clean out the libltdl3/ directory of all but the most recent, and then libtool will be just like any other library-providing package. -- Chuck