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: Wed, 13 Nov 2002 12:56:44 -0600 [thread overview]
Message-ID: <873cq5ti1f.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy765v1qx6c.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me> (Mikael Djurfeldt's message of "13 Nov 2002 10:58:03 -0500")
Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
> Without having thoroughly thought about it, I'd say it would be
> useful to be able to install parallel micro versions, the reason being
> that you may trust a certain micro version, but would like to do
> development on another.
If I understand correctly, then when you install the new "development"
micro version, it'll have a libguile with the same soname as the
"trusted" version, and at that instant, all apps will switch to using
the new "untrusted" lib because that's the one ldso will prefer
version-wise (that's presuming the new libguile doesn't just clobber
the old one if the micro version wasn't changed).
If I'm right about that, then are there any other arguments in favor
of not dropping the micro revision from things like the share
directory name, or would you be OK with it?
--
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-13 18:56 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
2002-11-13 15:58 ` Mikael Djurfeldt
2002-11-13 17:20 ` Rob Browning
2002-11-13 18:56 ` Rob Browning [this message]
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=873cq5ti1f.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).