From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Any opposition to changing share/guile/X.Y.Z to share/guile/X.Y?
Date: Tue, 12 Nov 2002 14:54:34 -0600 [thread overview]
Message-ID: <871y5qecfp.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy7el9qr503.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me> (Mikael Djurfeldt's message of "12 Nov 2002 13:56:44 -0500")
Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
> Hmm... shouldn't the libraries from different minor versions of Guile
> have different version numbers (bumbed between versions) and therefore
> be possible to install in parallel?
I should have been more specific -- I meant the revision number here,
what we call the MICRO version. i.e. 1.6.1 vs 1.6.2. Across those
two, I wouldn't necessarily (if perhaps at all -- see other msg)
expect the library version numbers to change.
For example, imagine the release was just a documentation update.
> Regarding the binary: How about using similar conventions as for
> emacs: guile symlinked to guile1.6.1
Do we want to support multiple installed MICRO revisions? i.e. do we
want it to be possible to install guile 1.6.1 and guile 1.6.2 side by
side? I was presuming we didn't specifically care about that, but if
we do, we probably can, but the changes will be more substantial since
we'll also have to start versioning the name of libguile,
i.e. libguile-12.so so that the .so development and .la dynamic
linking files won't clobber each other.
For Debian at least I was packaging things for now so that you can
only have one guile-X.Y-dev package installed at a time. To do
anything different would require more upstream changes (including the
above), and until/unless that happens, people should be able to get by
by just switching out the -dev packages.
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-12 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 17:47 Any opposition to changing share/guile/X.Y.Z to share/guile/X.Y? Rob Browning
2002-11-12 18:56 ` Mikael Djurfeldt
2002-11-12 20:54 ` Rob Browning [this message]
2002-11-13 15:58 ` Mikael Djurfeldt
2002-11-13 17:20 ` Rob Browning
2002-11-13 18:56 ` Rob Browning
2002-11-13 19:33 ` Mikael Djurfeldt
2002-11-13 19:53 ` Rob Browning
2002-11-14 17:14 ` tomas
2002-11-12 21:10 ` Andreas Rottmann
2002-11-12 22:12 ` Neil Jerram
2002-11-12 22:40 ` 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=871y5qecfp.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).