unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-user@gnu.org
Subject: Re: Managing Guile and extensions versions
Date: Mon, 03 Oct 2005 14:58:07 +0200	[thread overview]
Message-ID: <87zmpqlpuo.fsf@laas.fr> (raw)
In-Reply-To: <87d5mou19o.fsf@zip.com.au> (Kevin Ryde's message of "Sun, 02 Oct 2005 11:59:47 +1000")

Kevin Ryde <user42@zip.com.au> writes:

> I think difficulties with two .la's at the same time has been a
> more-or-less known issue for quite a while.  There may be plans afoot,
> but you might have observed the pace of libtool development is, well,
> glacial.  (No disrespect to the libtool developers, it's a big and
> arcane beast.)

Right (but I'm under the impression that Libtool releases are more
frequent than Guile releases ;-)).

> I believe it needs very careful thought, because it's about planning
> for or imagining what the future will look like, something that's far
> from settled.
>
> A system of versions virtually concedes that compatibility won't be
> maintained, and that some kind of perpetual revision or at least
> rebuilding of modules will be necessary.  It'd be better if that could
> be avoided.

Sure.  But while Guile developers can do their best to ensure that
Guile's modules don't change much over time, one cannot assume that
users of Guile won't ever need some versioning.

In actuality, versioning is something people have been expecting when
writing C code (and Libtool helps with this), and it's something which
other run-time supports, like Guile, should provide IMO.  Most of the
time, when one defines an API, be it in C or in Scheme, they cannot
guarantee that it won't ever change.

> I think the present seems worse than it is, because the last couple of
> releases have had a lot of changes.  If it settles down then the need
> to version stuff like crazy ought to vanish.

Right, but you're talking of Guile itself.

> The doco for the present is pretty light-on though.  Perhaps only
> power-users have gone beyond the basics. :-)  I'm not aware of any
> outright show-stoppers in the code though, not for any sensible sort
> of arrangement.

I'm not sure what you're talking about here.

Thanks,
Ludovic.


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


  parent reply	other threads:[~2005-10-03 12:58 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             ` Managing Guile and extensions versions Ludovic Courtès
2005-09-28 20:19               ` 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 [this message]
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=87zmpqlpuo.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).