From: tomas@fabula.de
Cc: Bruce Korb <bkorb@veritas.com>, rm@seid-online.de, guile-devel@gnu.org
Subject: Re: Should we distribute libltdl?
Date: Wed, 9 Mar 2005 16:49:51 +0100 [thread overview]
Message-ID: <20050309154951.GB14046@www> (raw)
In-Reply-To: <lj3bv4svqg.fsf@troy.dt.e-technik.uni-dortmund.de>
[-- Attachment #1.1: Type: text/plain, Size: 1206 bytes --]
On Wed, Mar 09, 2005 at 04:08:07PM +0100, Marius Vollmer wrote:
> rm@seid-online.de writes:
>
> > Can't guile distribute libltdl but only use
> > it iff there's no local version found (or if the user states her
> > intention by configure magic)?
>
> That is how it works right now. I am not happy about the fact that
> Guile does this silently and that it is a configure decision that
> persists in the build tree.
>
> What I would be happy with is to include a copy of libltdl in the
> Guile distribution but to have it completely ignored by configure and
> the Makefiles. When libltdl is not found in the system, a message
> could be printed that instructs the user to install libltdl, maybe by
> using the included sources.
Makes the most sense to me too. This way a user can decide whether
to let her packaging system deal with it or not.
Installing silently libltdl can be a source of woes (even statically
linking it, since Guile can be linked to other apps which themselves
may use a slightly different version of libltdl: watch Apache and
expat coming in differently via different modules: hours of fun).
Regards -- and thanks for the great work again
-- tomás
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-03-09 15:49 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 [this message]
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=20050309154951.GB14046@www \
--to=tomas@fabula.de \
--cc=bkorb@veritas.com \
--cc=guile-devel@gnu.org \
--cc=rm@seid-online.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).