From: Rob Browning <rlb@defaultvalue.org>
Subject: Regarding (bug "versioning-of-extensions")
Date: Thu, 28 Mar 2002 15:27:51 -0600 [thread overview]
Message-ID: <87eli4bcx4.fsf@raven.i.defaultvalue.org> (raw)
As our temporary fix for 1.6, it looks like it's going to be easy to
switch to adding the INTERFACE number to the end of the lib, i.e.
libguilesrfi-srfi-13-14_15.so.X.Y.Z
and for now I'm using an underscore to separate out the version number
from the library name[1].
However, as you may or may not know, when you specify the three
library versioning numbers to libtool, you're *not* specifying the
major.minor.revision numbers for the lib -- libtool computes those
from what you give it based on its versioning semantics.
For example, right now we have an INTERFACE_VERSION for guile-readline
of 15 and an INTERFACE_AGE of 1 in
guile-readline/LIBGUILEREADLINE-VERSION. This will cause libtool to
build
libguilereadline_15.so.14.2.0
Note the "13" rather than a "15". So our _15 in the name won't
actually match the real major number of the lib. I'm not sure this
really matters, since all we really need is for the names of these
libs to be unique and to not match either guile 1.3.4 or 1.4's names
or guile 1.8 and above's, but I thought I'd point it out in case
someone else sees a problem.
Thanks
[1] for now -- I may need to change this since it might make packaging
guile 1.6 for Debian a little harder than necessary
--
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 reply other threads:[~2002-03-28 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-28 21:27 Rob Browning [this message]
2002-04-01 2:17 ` Regarding (bug "versioning-of-extensions") Rob Browning
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=87eli4bcx4.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).