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 13:53:28 -0600 [thread overview]
Message-ID: <87k7jhqm9z.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <xy765v12rke.fsf@linnaeus.i-did-not-set--mail-host-address--so-shoot-me> (Mikael Djurfeldt's message of "13 Nov 2002 14:33:05 -0500")
Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
> I have no other argument. Also, it is "OK" with me to do as you want,
> because I haven't the time to think about it.
>
> But if you ask my current uninformed opinion, and given the current
> poor status of UNIX tool for handling this kind of dependencies, I'd
> say I prefer separating micro versions and recompiling things between
> micro version releases. :)
Well it certainly would fix the problem in some sense, but unless
we're going to make guile "Depends: gcc", and switch to a "compile on
install" packaging arrangement (don't think I haven't considered that
-- actually having gcc around all the time might open up some
"interesting" compilation options), I suspect we might have a revolt
from the users tracking Debian unstable if all guile packages broke
with every minor release :>
Though I guess if we put the full version in the lib names and in
*everything* else (like libguile-1.6.1.so,
libguile-srfi-srfi-4-v-1.6.0.so etc.) then we could just eat a lot of
disk space rather than break things with new releases, but I also
suspect that the first time one of the other Debian maintainers
noticed that they had all of the
guile-1.6.1
guile-1.6.2
guile-1.6.3
guile-1.8.1
guile-1.8.2
packages installed at the same time (due to leftovers), I might have
to think fast if I wanted to avoid a good trouncing :>
--
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 19:53 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
2002-11-13 19:33 ` Mikael Djurfeldt
2002-11-13 19:53 ` Rob Browning [this message]
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=87k7jhqm9z.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).