unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: Should we distribute libltdl?
Date: Tue, 08 Mar 2005 17:57:48 +0100	[thread overview]
Message-ID: <ljwtsirs6r.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <rmiekeqkuvf.fsf@fnord.ir.bbn.com> (Greg Troxel's message of "08 Mar 2005 10:41:40 -0500")

Greg Troxel <gdt@ir.bbn.com> writes:

> A big question is the ease of installation for those using OS package
> systems vs those doing things by hand.  My view is that the really big
> issue is making things
> a) easy to package
> and
> b) easy to use once packaged

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.

> Here's the guile control file for pkgsrc.  But it seems to link in the
> special guile ltldl:

Yes, in the 1.6 series we use our own version of libltdl.  This is no
longer the case.


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


  reply	other threads:[~2005-03-08 16:57 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 [this message]
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=ljwtsirs6r.fsf@troy.dt.e-technik.uni-dortmund.de \
    --to=marius.vollmer@uni-dortmund.de \
    --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).