From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel <guix-devel@gnu.org>, "guix-hpc@gnu.org" <guix-hpc@gnu.org>
Subject: Re: [rb-general] Paper preprint: Reproducible genomics analysis pipelines with GNU Guix
Date: Fri, 11 May 2018 10:19:54 +0200 [thread overview]
Message-ID: <87603ufvth.fsf@elephly.net> (raw)
In-Reply-To: <878t8qr4t0.fsf@inria.fr>
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
> Perhaps we could add to Autoconf-Archive (if it doesn’t have such things
> already) macros to deal with the R and Python stuff you had to deal
> with? And then publish a simple template that people could use as a
> starting point.
I submitted my macros for R packages (and they have been accepted), but
I actually don’t really like them because they are not as useful as it
may seem. While they do check for R packages in the environment at
configure time, nothing is done to record the environment necessary to
access these packages.
That’s a general problem for software that depends on search path
environment variables. I can’t just record the location of each
individual R package that was detected and use that to set up the
environment at runtime. The R packages have other runtime dependencies
that would also need to be recorded.
It’s not ideal.
--
Ricardo
next prev parent reply other threads:[~2018-05-11 8:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 12:18 Paper preprint: Reproducible genomics analysis pipelines with GNU Guix Ricardo Wurmus
2018-04-11 18:30 ` [rb-general] " Holger Levsen
2018-04-11 18:40 ` Ricardo Wurmus
2018-04-11 19:00 ` Holger Levsen
2018-04-11 18:31 ` Holger Levsen
2018-04-11 21:16 ` Roel Janssen
2018-04-15 7:50 ` Amirouche Boubekki
2018-04-23 8:20 ` [rb-general] " Ludovic Courtès
[not found] ` <87fu30fsra.fsf@elephly.net>
2018-05-11 8:10 ` Ludovic Courtès
2018-05-11 8:19 ` Ricardo Wurmus [this message]
2018-05-11 9:39 ` Catonano
2018-05-13 5:07 ` Ricardo Wurmus
2018-05-13 8:58 ` Catonano
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=87603ufvth.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=guix-hpc@gnu.org \
--cc=ludovic.courtes@inria.fr \
/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.