From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: packaging the add-on libs...
Date: Thu, 10 Oct 2002 10:22:42 -0500 [thread overview]
Message-ID: <87lm56co8t.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20021010071246.GA29109@www> (tomas@fabula.de's message of "Thu, 10 Oct 2002 09:12:46 +0200")
tomas@fabula.de writes:
> At the risk of boring you all (or even of being flamed out of the
> list ;-) I'd like to repeat what has been (or is being) discussed
> in another thread. The Big Guys (those with the P in the name, you
> remember) have version-dependent [1] subdirectories where they
> stuff the modules into which `belong' to the interpreter [2]. This
> is a strategy also followed by Emacs. I think this approach might
> minimize the problems you expose above.
It's been stated that we're going to keep all the directly linkable
libs in the "normal place". 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.
> Of course, Marius is right in not wanting to introduce gratuitous
> dependencies and trying to distribute modules which are usable as
> either guile extensions or as shared libs on their own. But those
> shouldn't care about which guile version they are linked against (or
> even whether there is guile around at all), and I'd expect them to
> provide some (even if stripped down) functionality in any case.
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.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-10 15:22 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 [this message]
2002-10-11 9:41 ` tomas
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=87lm56co8t.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).