unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: linasvepstas@gmail.com
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile release planning
Date: Sat, 15 Nov 2008 23:16:04 +0000	[thread overview]
Message-ID: <49dd78620811151516l2f59808co2af6d1f38cd3db9c@mail.gmail.com> (raw)
In-Reply-To: <3ae3aa420811101944m23d7a72ch992c253326f7e236@mail.gmail.com>

2008/11/11 Linas Vepstas <linasvepstas@gmail.com>:
>
> Any ideas for binary compatibility for the "micro" revisions?

At our "upstream" level (i.e. not trying to solve all of the
distribution-level issues), I think the theory is that this is covered
by library interface numbering.  In other words, if a change in guile
causes the new libguile not to be compatible with the previous one,
libguile's revision number should be incremented.

> I recently discovered that a library compiled against 1.8.3
> would core dump when used with an application compiled
> against 1.8.5.

And I assume the actually loaded libguile was version 1.8.5?  So there
should have been something in the library saying that it needed 1.8.3,
which would have caused the link to fail.  Does the libtool scheme
cover this; I'm afraid I just don't know.

> The linux kernel got rid of the stable/unstable branch idea,
> and it's worked really really well. (the reasons why are
> widely documented) I'm for it.

Yes, I guess my suggestion is quite similar to what the kernel did.

Thanks,
   Neil




  parent reply	other threads:[~2008-11-15 23:16 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11  1:23 Guile release planning Neil Jerram
2008-11-11  1:59 ` Mike Gran
2008-11-15 23:03   ` Neil Jerram
2008-11-15 23:19     ` Mike Gran
2008-11-11  3:18 ` Jon Wilson
2008-11-15 23:05   ` Neil Jerram
2008-11-19  3:54     ` Jon Wilson
2008-11-11  3:44 ` Linas Vepstas
2008-11-11 17:10   ` Greg Troxel
2008-11-11 20:00   ` Andy Wingo
2008-11-11 21:05     ` Linas Vepstas
2008-11-11 22:06       ` Andy Wingo
2008-11-11 20:18   ` Ludovic Courtès
2008-11-15 23:16   ` Neil Jerram [this message]
2008-11-16 23:33     ` Ludovic Courtès
2008-11-17 20:49       ` Andy Wingo
2008-11-18 10:22         ` Ludovic Courtès
2008-12-08 22:05           ` Neil Jerram
2008-12-09 17:01             ` Ludovic Courtès
2008-11-11 15:32 ` Sebastian Tennant
2008-11-11 20:30 ` Ludovic Courtès
2008-11-16  0:03   ` Neil Jerram
2008-11-16  5:11     ` Linas Vepstas
2008-11-16 12:46     ` Greg Troxel
2008-11-16 23:55     ` Ludovic Courtès
2008-11-11 23:00 ` Andy Wingo
2008-11-12 10:11   ` Ludovic Courtès
2008-11-12 19:15     ` Andy Wingo
2008-11-12  4:41 ` Han-Wen Nienhuys
2008-11-12 19:11   ` Andy Wingo

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=49dd78620811151516l2f59808co2af6d1f38cd3db9c@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=linasvepstas@gmail.com \
    /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).