unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Any opposition to changing share/guile/X.Y.Z to share/guile/X.Y?
Date: Tue, 12 Nov 2002 11:47:09 -0600	[thread overview]
Message-ID: <87u1imiste.fsf@raven.i.defaultvalue.org> (raw)


I'm working on the packaging of 1.6 for Debian, and I wondered if
anyone would oppose dropping the minor revision number from guile's
working directory.  The argument against would be that it isn't as
specific and would prevent you from having two minor revisions of
guile installed in the same place at the same time, but you can't do
that anyway since their library, binary, etc. names would collide.

The argument in favor is that it means that any other guile "add-on"
packages that are guile version sensitive can place a symlink (or a
copy) of their .scm dir in share/guile/X.Y/ without having to worry
about the directory being yanked out from under them when the guile
package goes from 1.6.1 to 1.6.2.

-- 
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


             reply	other threads:[~2002-11-12 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 17:47 Rob Browning [this message]
2002-11-12 18:56 ` Any opposition to changing share/guile/X.Y.Z to share/guile/X.Y? 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
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=87u1imiste.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).