From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Greg Troxel <gdt@ir.bbn.com>,
guile-devel@gnu.org,
Marius Vollmer <marius.vollmer@uni-dortmund.de>
Subject: Re: Should we distribute libltdl?
Date: Tue, 08 Mar 2005 18:36:38 +0000 [thread overview]
Message-ID: <422DF0B6.4090807@ossau.uklinux.net> (raw)
In-Reply-To: <87oedu2fql.fsf@trouble.defaultvalue.org>
Rob Browning wrote:
> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>
>
>>Those two things would benefit when Guile explicitely declares as a
>>external dependency. The Right Thing for a Guile OS package such as a
>>.deb or .rpm is not to contain libltdl but to depend on the package
>>that contains libltdl.
>
>
> For the record, now that we don't need customizations, I don't have
> any problem with dropping our copy of libltdl. Alhough I agree that
> it would be good to have a clear configure error message when libltdl
> is not detected.
>
That's my view too. Perhaps I'm spoilt by being a Debian user, but if
other OS's don't have a decent package system, they really ought to sort
that out.
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-03-08 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-08 1:09 Should we distribute libltdl? Marius Vollmer
2005-03-08 1:51 ` 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 [this message]
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=422DF0B6.4090807@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=gdt@ir.bbn.com \
--cc=guile-devel@gnu.org \
--cc=marius.vollmer@uni-dortmund.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).