unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: libguile-ltdl
Date: Wed, 06 Oct 2004 20:31:49 -0500	[thread overview]
Message-ID: <871xgb1fga.fsf@trouble.defaultvalue.org> (raw)
In-Reply-To: <16740.30007.983868.166131@byrd.xs4all.nl> (Han-Wen Nienhuys's message of "Thu, 7 Oct 2004 00:44:07 +0200")

Han-Wen Nienhuys <hanwen@xs4all.nl> writes:

> If there is a need for urgent bugfixes or more features in ltdl, then
> they can contributed to libtool, or (in extreme cases) libtool itself
> can be forked.

This is exactly what happened.  There were a number of attempts to
talk to the libtool upstream over a substantial period of time without
any response, though from a look at the eventual fixes that made it
in, they did eventually receive and apply our fixes.  If it hadn't
been for those communication difficulties, we probably never would
have created libguile-ltdl.

In any case, other than the possibility that we might want to add a
versioned dlopen (and that's only relevant if we're still sure we want
that, and if the libtool upstream wouldn't be interested), it looks
like the other reasons for having libguile-ltdl have been eliminited
by upstream fixes.

I'd like to see what Marius thinks, but we might be able to remove
libguile-ltdl in 1.7 now.  I'd be more hesitant to do so in 1.6,
unless it was only for cygwin.  Removing a library isn't a backward
compatible change.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2004-10-07  1:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 22:36 libguile-ltdl Han-Wen Nienhuys
2004-09-28 22:54 ` libguile-ltdl Rob Browning
2004-10-06 22:44   ` libguile-ltdl Han-Wen Nienhuys
2004-10-07  1:31     ` Rob Browning [this message]
2004-10-07  7:48       ` libguile-ltdl Han-Wen Nienhuys
2004-10-07 15:11         ` libguile-ltdl Rob Browning
2004-10-07  7:52       ` libguile-ltdl Han-Wen Nienhuys
2004-10-07 15:17         ` libguile-ltdl Rob Browning
2004-10-07 18:35           ` libguile-ltdl Han-Wen Nienhuys
2004-10-18 16:28       ` libguile-ltdl Marius Vollmer
2004-10-18 16:32     ` libguile-ltdl Marius Vollmer

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871xgb1fga.fsf@trouble.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    /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).