From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: 1.6.0: major soname version decremented?
Date: Mon, 23 Sep 2002 09:06:45 -0500 [thread overview]
Message-ID: <873cs0kdfu.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <8765wxdjr8.fsf@peder.flower> (Jan Nieuwenhuizen's message of "Mon, 23 Sep 2002 13:32:11 +0200")
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> Yes, I know. But 1.5.x has been stable for almost a year; that's what
> we've been using for LilyPond, and that's where (Cygwin compatibility)
> development was merged.
But as long as LilyPond didn't deploy a version publically using
1.5.X, then I wouldn't expect there to be a problem...
>> The reason for the decrement is that Thien-Thi asked that I add some
>> (libtool) "AGE" to the libraries and that seemed reasonable so I did.
>> This decremented the major number.
>
> Aahh, the wonders of libtool. You're not telling me that libtool is
> in control, rather than the developers? ;-)
Nope. I knew it would decrease the major number, I just didn't think
it would matter. If this *is* in fact a big problem, please explain,
and we'll figure out what should be done about it.
--
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-09-23 14:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-20 11:45 1.6.0: major soname version decremented? Jan Nieuwenhuizen
2002-09-20 21:17 ` Rob Browning
2002-09-23 11:32 ` Jan Nieuwenhuizen
2002-09-23 14:06 ` Rob Browning [this message]
2002-09-23 14:15 ` Jan Nieuwenhuizen
2002-09-23 15:25 ` Rob Browning
[not found] ` <p05100300b9b4e79b92b9@[128.174.103.145]>
2002-09-23 16:27 ` Jan Nieuwenhuizen
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=873cs0kdfu.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).