unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: add-on lib versioning (concrete example g-wrap) -- what to do?
Date: 14 Dec 2002 17:02:12 +0100	[thread overview]
Message-ID: <87wumcoagr.fsf@zagadka.ping.de> (raw)
In-Reply-To: <87d6o7vvat.fsf@raven.i.defaultvalue.org>

Rob Browning <rlb@defaultvalue.org> writes:

> FWIW I'd also like to point out that this is definitely a point
> against guile in the broader "which language should I use for X
> project" arena.  I've actually seen it have a negative impact.  I also
> suspect that unless we address this, it's may be difficult for our
> outside guile-core "add-on" base to grow and maintain much long-term
> stability.

But is it a genuine Guile problem?  What is the difference between
libguile and, say, libX11?  Libguile is changing incompatibly much
more often than libX11 is, and people don't want to have multiple
incompatible versions of libX11 on their system simultaneously.

So we should probably works towards that as well: we should give
people no reason to want to compile new software against Guile 1.4.
Why do they want this?

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


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


  parent reply	other threads:[~2002-12-14 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 20:25 add-on lib versioning (concrete example g-wrap) -- what to do? Rob Browning
2002-12-13  8:47 ` tomas
2002-12-13 21:37 ` Christopher Cramer
2002-12-13 22:53   ` Rob Browning
2002-12-14 16:02 ` Marius Vollmer [this message]
2002-12-14 18:47   ` 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=87wumcoagr.fsf@zagadka.ping.de \
    --to=mvo@zagadka.ping.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).