From: Marius Vollmer <mvo@zagadka.de>
Subject: Should we distribute libltdl?
Date: Tue, 08 Mar 2005 02:09:19 +0100 [thread overview]
Message-ID: <87sm37vt8g.fsf@zagadka.de> (raw)
Hi,
we currently distribute a copy of libltdl as part of guile-core and
install it when libltdl is not already found in the system.
I think this is wrong since libltdl belongs to libtool and should be
installed by libtool and not by any number of programs that use it.
We do not distribute libgmp although we rely on it and we shouldn't
distribute libltdl although we rely on it.
I had the concrete problem that I couldn't do a "make distcheck"
without prior "make install" on a system where in fact libltdl was not
available. But even if this is due to some bugs in the way that we
use libltdl, I think we should just treat libltdl as any other
external library.
It makes installing Guile slightly harder, but the behavior of Guile
is in fact simpler.
Opinions?
(I have committed the removal of libltdl already.)
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2005-03-08 1:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 1:09 Marius Vollmer [this message]
2005-03-08 1:51 ` Should we distribute libltdl? Bruce Korb
2005-03-08 16:53 ` Marius Vollmer
2005-03-08 17:13 ` Bruce Korb
2005-03-08 17:41 ` Marius Vollmer
2005-03-08 17:45 ` rm
2005-03-09 15:08 ` Marius Vollmer
2005-03-09 15:49 ` tomas
2005-03-09 16:20 ` Rob Browning
2005-03-08 23:10 ` Greg Troxel
2005-03-08 15:41 ` Greg Troxel
2005-03-08 16:57 ` Marius Vollmer
2005-03-08 17:45 ` Rob Browning
2005-03-08 18:36 ` Neil Jerram
2005-03-09 15:08 ` 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=87sm37vt8g.fsf@zagadka.de \
--to=mvo@zagadka.de \
/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).