unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Julian Graham <joolean@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: r6rs libraries, round two
Date: Mon, 6 Jul 2009 14:02:42 -0400	[thread overview]
Message-ID: <2bc5f8210907061102u11194448n50baa72b3c69985b@mail.gmail.com> (raw)
In-Reply-To: <m3skhkyr3l.fsf@pobox.com>

Hi Andy,


> Back to your question though, what did you think about my symlink
> solution[1]?
>
> [1] http://article.gmane.org/gmane.lisp.guile.devel/8585

It's fine, although any length suffix of a version specifier can be
omitted in the case of a match -- that is, you can do without the
version altogether, or you can just partially specify a version; in
both cases, the system needs to find a matching version for you.
Would the symlinking strategy you describe happen at every node in the
directory tree of versions for a particular library?

E.g., let's say you've got version 1.2.3 of R6RS library `(foo bar)'
installed.  Does the installation directory look like:

foo/1/2/3/bar.scm
foo/1/2/bar.default -> foo/1/2/3/bar.scm
foo/1/bar.default -> foo/1/2/3/bar.scm
foo/bar.default -> foo/1/2/3/bar.scm


Regards,
Julian




      parent reply	other threads:[~2009-07-06 18:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 20:31 r6rs libraries, round two Julian Graham
2009-05-30 23:22 ` Neil Jerram
2009-05-30 23:34   ` Julian Graham
2009-06-01 19:55   ` Andy Wingo
2009-06-01 22:34     ` Ludovic Courtès
2009-06-03 18:36       ` Neil Jerram
2009-06-04  6:50         ` Ludovic Courtès
2009-06-28  0:20       ` Julian Graham
2009-06-28 13:28         ` Neil Jerram
2009-06-28 18:23           ` Julian Graham
2009-06-28 21:40         ` Andy Wingo
2009-06-29 18:01           ` Julian Graham
2009-06-29 18:26             ` Ludovic Courtès
2009-07-06 18:02           ` Julian Graham [this message]

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=2bc5f8210907061102u11194448n50baa72b3c69985b@mail.gmail.com \
    --to=joolean@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.com \
    /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).