From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: packaging the add-on libs...
Date: Fri, 11 Oct 2002 11:41:50 +0200 [thread overview]
Message-ID: <20021011094150.GA3235@www> (raw)
In-Reply-To: <87lm56co8t.fsf@raven.i.defaultvalue.org>
On Thu, Oct 10, 2002 at 10:22:42AM -0500, Rob Browning wrote:
> tomas@fabula.de writes:
>
[...]
> It's been stated that we're going to keep all the directly linkable
> libs in the "normal place".
Yes, I know (that's why I know I was taking risks ;-). I felt uneasy
then and still feel uneasy abut it (see below).
> That means /usr/lib, and that would apply
> to all the add-on libs so far (i.e. we don't have any non-directly C
> linkable) add-on libs right now.
>
> I guess you could argue for a versioned directory for any new shared
> libs that aren't supposed to be directly linkable by any other apps or
> libs.
Yes, kind of. Only that I'd substitute ``that aren't supposed to be
directly linkable by'' for ``that have to go with guile to be linked
by...''
In other words, if you need guile in conjunction with libfoo, then
libfoo has no business in /usr/lib or /usr/local/lib -- but rather
in /usr/lib/guile/1.6/ (or something like that). IMHO, of course.
[snip]
> These libraries *have* to care about which guile version they're
> linked against. For example, libguile-srfi-srfi-4-v-1 *has* to be
> linked against libguile12 so it can use even primitive operations like
> car and cdr. And of course libguile12 depends intimately on the
> particular source in ice-9/ that it comes with. There's no such thing
> as a stand-alone guile module/shared-lib. If they don't depdend on
> libguileX, they can't *do* anything -- no car, no cdr, no GC, etc.
Well -- one could imagine (say) some regexp library or some DBM library
which is delivered with guile but would make sense as a stand-alone.
If it's possible to keep the glue code separate, it might be possible
to make it guile-independent (my hazy memory suggests SDBM from Perl
as an example, but may be I'm forgetting important bits here).
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-11 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 5:03 packaging the add-on libs Rob Browning
2002-10-10 7:12 ` tomas
2002-10-10 15:22 ` Rob Browning
2002-10-11 9:41 ` tomas [this message]
2002-10-11 15:59 ` Rob Browning
2002-10-14 11:34 ` tomas
2002-10-11 16:14 ` Rob Browning
2002-10-11 17:10 ` Greg Troxel
2002-10-11 18:26 ` Rob Browning
2002-10-11 20:37 ` Greg Troxel
2002-10-10 12:51 ` Greg Troxel
2002-10-10 15:37 ` Rob Browning
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=20021011094150.GA3235@www \
--to=tomas@fabula.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).