From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28157@debbugs.gnu.org
Subject: bug#28157: “r-minimal” retains no reference to “which”
Date: Tue, 22 Aug 2017 11:19:45 +0200 [thread overview]
Message-ID: <8760dgvu1a.fsf@elephly.net> (raw)
In-Reply-To: <877exwc7eh.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> R provides a function “Sys.which”, which embeds the full path to “which”
>> at configure time. The path it embeds is that of “which” *before*
>> grafts.
>
> Where’s that reference? I couldn’t find it:
You can see the reference (before commit
a8cd352304807ef60d06c35da07c5456f036688c) within an R session. If you
type “Sys.which” the code for “Sys.which” will be printed.
$ /gnu/store/hzc1fnrjv8ys399glbzmhds21fm9zzva-r-minimal-3.4.0/bin/R -e 'Sys.which' | grep /gnu/store
which <- "/gnu/store/ppyczjc1figwv6yb6brg938y49856avb-which-2.21/bin/which"
(The reference is the same as “guix build --no-grafts which”.)
> Normally the grafting code replaces all the store references, unless the
> reference is somehow obfuscated (which would be surprising here.)
Right. In the case of R, the environment for a package is serialized to
a possibly compressed data file (.Rdb) with an index (.Rdx).
“Sys.which” is part of the “base” package and I cannot find a plain text
reference to “bin/which” in the binaries for “base”.
I don’t know if we can (or should) disable compression for Rdb files.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-08-22 9:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 11:16 bug#28157: “r-minimal” retains no reference to “which” Ricardo Wurmus
2017-08-22 8:51 ` Ludovic Courtès
2017-08-22 9:19 ` Ricardo Wurmus [this message]
2017-08-22 9:29 ` Ricardo Wurmus
2017-08-22 9:38 ` Ludovic Courtès
2017-08-22 11:02 ` Ricardo Wurmus
2017-08-22 13:40 ` Ludovic Courtès
2017-08-22 14:03 ` Ricardo Wurmus
2017-08-22 14:33 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760dgvu1a.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=28157@debbugs.gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.