From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: Any opposition to changing share/guile/X.Y.Z to share/guile/X.Y?
Date: 13 Nov 2002 10:58:03 -0500 [thread overview]
Message-ID: <xy765v1qx6c.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me> (raw)
In-Reply-To: <871y5qecfp.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> 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.
Well, that's what I meant as well.
> 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,
Marius and you have to have the final say about this.
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.
> 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.
Maybe that would be a great idea. I've been trying to keep a
system-level production version of guile-1.4 installed under /usr/lib
in parallel with an experimental guile-1.7.0 under /usr/local/lib.
A real nuisance has been that the libtool-generated link flags contain
both -L /usr/lib and -L /usr/local/lib in a somewhat arbitrary order.
I tried to resolve this, but finally got so frustrated that I simply
moved away all libraries under /usr/lib while compiling guile-1.7.0...
> 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.
Are you sure, considering what I wrote above?
It seems to me that we'll have trouble as long as we don't include the
version in the library names...
Mikael
_______________________________________________
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 15:58 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 [this message]
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=xy765v1qx6c.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me \
--to=mdj@kvast.blakulla.net \
--cc=djurfeldt@nada.kth.se \
--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).