From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Mailing List: CygWin-Apps <cygwin-apps@cygwin.com>
Subject: Re: accumulated upset warnings: clisp, gnome, ImageMagick, libtool, clamav, gnutls, guile, jasper, tetex, guile
Date: Wed, 20 Aug 2008 19:23:00 -0000 [thread overview]
Message-ID: <48AC6EF7.80302@cwilson.fastmail.fm> (raw)
In-Reply-To: <20080820173026.GA9685@ednor.casa.cgf.cx>
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
next prev parent reply other threads:[~2008-08-20 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 4:35 Christopher Faylor
2008-08-20 5:17 ` Charles Wilson
2008-08-20 5:50 ` Yaakov (Cygwin Ports)
2008-08-20 7:06 ` Reini Urban
2008-08-20 15:57 ` Christopher Faylor
2008-08-20 16:08 ` Corinna Vinschen
2008-08-20 16:43 ` Charles Wilson
2008-08-20 17:31 ` Christopher Faylor
2008-08-20 19:23 ` Charles Wilson [this message]
2008-08-31 4:33 ` Yaakov (Cygwin Ports)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48AC6EF7.80302@cwilson.fastmail.fm \
--to=cygwin@cwilson.fastmail.fm \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).