From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Regarding (bug "versioning-of-extensions")
Date: Sun, 31 Mar 2002 20:17:10 -0600 [thread overview]
Message-ID: <871ye0f9i1.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87eli4bcx4.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 28 Mar 2002 15:27:51 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
> and for now I'm using an underscore to separate out the version
> number from the library name[1].
Unless there are objections, I think I'm going to leave the number
alone, i.e. use 15, even though due to AGE the actual lib major
version might be smaller, for example 13, but I'll change the naming
scheme like this
libguile-srfi-srfi-13-14-lt15
The lt15 will reflect the libtool interface, and should make it clear
that something unusual is going on. We'll also have details in NEWS,
and perhaps the info files. Since these ltFOO versions will only
exist for 1.6, ugly names aren't such a big deal -- they should be
going away fairly soon.
Thanks
--
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-04-01 2:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 21:27 Regarding (bug "versioning-of-extensions") Rob Browning
2002-04-01 2:17 ` Rob Browning [this message]
2002-04-01 5:49 ` Rob Browning
2002-04-03 4:27 ` 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=871ye0f9i1.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.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).