From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Managing Guile and extensions versions
Date: Wed, 28 Sep 2005 09:10:46 +0200 [thread overview]
Message-ID: <87d5mtis5l.fsf_-_@laas.fr> (raw)
In-Reply-To: <6efab235050927101826b2da7d@mail.gmail.com> (Vorfeed Canal's message of "Tue, 27 Sep 2005 21:18:30 +0400")
Hi,
Vorfeed Canal <vorfeed.canal@gmail.com> writes:
> Of course it must - how else can it load them ? With my patch it knows
> about few default places and can be instructed about other places in
> nice shemely way.
Yes, your patch seems to be one possible solution. However, why not use
`pkglibdir' (versionizing it) which you mentioned in earlier posts
instead of this new directory?
The other thing needed, which you also mentioned earlier, is to have a
versionized site directory. I've actually always wondered why this one
was not versioned.
>> This is true I guess, because `dynamic-link' doesn't allow to specify
>> version info. _This_ is an issue and maybe this procedure could be
>> fixed by allowing the user to pass Libtool-like version information.
>
> This is one solution. And IMO not the best solution.
That's a solution to one of the two problems, the two problems being:
1. Separating C libraries that are written for different versions of
Guile, allowing to have versions of the same extension written for
different Guile versions to coexist;
2. Allowing to have different versions of a given extension for a same
version of Guile.
Your patch addresses (1). This `dynamic-link' thing could be used to
address (2). It could be used to address (1) instead, but certainly not
both of them. Anyway, we'd first need `libltdl' to allow for such
things. I started to ask the Libtool people about this:
http://lists.gnu.org/archive/html/libtool/2005-09/msg00118.html .
Thanks,
Ludovic.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-09-28 7:10 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-25 21:50 PHP to GUILE Vorfeed Canal
2005-09-26 1:42 ` Kevin Ryde
2005-09-26 7:27 ` Zeeshan Ali
2005-09-26 8:17 ` Vorfeed Canal
2005-09-26 17:57 ` Zeeshan Ali
2005-09-26 19:05 ` Vorfeed Canal
2005-09-26 19:34 ` Zeeshan Ali
2005-09-26 7:43 ` Vorfeed Canal
2005-09-26 11:17 ` Thien-Thi Nguyen
[not found] ` <6efab23505092609331abd82b7@mail.gmail.com>
2005-09-26 16:34 ` Vorfeed Canal
2005-09-26 22:12 ` Thien-Thi Nguyen
2005-09-27 10:11 ` Vorfeed Canal
2005-09-27 12:48 ` Thien-Thi Nguyen
2005-09-27 14:36 ` Vorfeed Canal
2005-09-27 17:13 ` Thien-Thi Nguyen
2005-09-27 17:47 ` Vorfeed Canal
2005-09-27 19:44 ` Thien-Thi Nguyen
2005-09-26 12:23 ` Exceptions Ludovic Courtès
2005-09-26 19:20 ` Exceptions Vorfeed Canal
2005-09-27 8:42 ` Exceptions Ludovic Courtès
2005-09-27 10:54 ` Exceptions Vorfeed Canal
2005-09-27 15:45 ` Exceptions Ludovic Courtès
2005-09-27 17:18 ` Exceptions Vorfeed Canal
2005-09-28 7:10 ` Ludovic Courtès [this message]
2005-09-28 20:19 ` Managing Guile and extensions versions Vorfeed Canal
2005-09-29 15:34 ` Ludovic Courtès
2005-09-29 16:30 ` Vorfeed Canal
2005-09-30 22:07 ` Neil Jerram
2005-10-19 7:58 ` Rob Browning
2005-09-29 22:24 ` Kevin Ryde
2005-09-30 8:00 ` Ludovic Courtès
2005-10-02 1:59 ` Kevin Ryde
[not found] ` <6efab2350510020425j76899e29hec6ea7e3dcce6c3@mail.gmail.com>
2005-10-03 1:58 ` Kevin Ryde
2005-10-04 11:06 ` Vorfeed Canal
2005-10-04 23:58 ` Kevin Ryde
2005-10-05 14:18 ` Vorfeed Canal
2005-10-09 1:53 ` Kevin Ryde
2005-10-11 10:20 ` Vorfeed Canal
2005-10-11 14:56 ` Greg Troxel
2005-10-11 21:32 ` Kevin Ryde
2005-10-03 12:58 ` Ludovic Courtès
2005-09-26 19:37 ` PHP to GUILE Neil Jerram
[not found] ` <6efab235050926131843ce69e2@mail.gmail.com>
2005-09-26 20:18 ` Vorfeed Canal
2005-09-26 22:39 ` Kevin Ryde
2005-09-27 9:20 ` Vorfeed Canal
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=87d5mtis5l.fsf_-_@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-user@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).