From: Ricardo Wurmus <rekado@elephly.net>
To: divoplade <d@divoplade.fr>
Cc: help-guix@gnu.org
Subject: Re: Wrapping an R script: how do I compose the R_LIBS_SITE environment variable?
Date: Sun, 07 Feb 2021 08:11:27 +0100 [thread overview]
Message-ID: <87v9b4s674.fsf@elephly.net> (raw)
In-Reply-To: <e5ffcd89fcc2211d9934bccd97fd8c92122c434d.camel@divoplade.fr>
divoplade <d@divoplade.fr> writes:
> Attached is an example of a script written in R that has non-trivial
> recursive dependencies.
Why don’t you use the r-build-system here?
> If you look at the package definition, you see that I call wrap-program
> in order to set the R_LIBS_SITE environment variable. The components of
> R_LIBS_SITE is the R dependencies of my package, and their recursive R
> dependencies. But I don't know how to get them.
The r-build-system has a procedure “generate-site-path” to generate
R_LIBS_SITE.
--
Ricardo
next prev parent reply other threads:[~2021-02-07 7:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 16:14 Wrapping an R script: how do I compose the R_LIBS_SITE environment variable? divoplade
2021-02-06 13:53 ` zimoun
2021-02-06 15:28 ` Ricardo Wurmus
2021-02-07 0:24 ` divoplade
2021-02-07 7:11 ` Ricardo Wurmus [this message]
2021-02-07 9:30 ` divoplade
2021-02-07 15:03 ` zimoun
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9b4s674.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=d@divoplade.fr \
--cc=help-guix@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).