From: myglc2 <myglc2@gmail.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: r: Update to 3.3.1.
Date: Mon, 01 Aug 2016 16:59:11 -0400 [thread overview]
Message-ID: <86wpk0gq8w.fsf@gmail.com> (raw)
In-Reply-To: 874m745kci.fsf@elephly.net
Ricardo Wurmus <rekado@elephly.net> writes:
> myglc2 <myglc2@gmail.com> writes:
>
>> I imagine that, in the spirit of guix, we also want a user to be able to
>> "help themself" instead of depending on a 'manager.' This would probably
>> require an additional R "package manager component" that is usable by a
>> manager or user. Such a thing would certainly showcase the unique
>> capabilities of guix.
>
> We have importers that generate Guix package expressions from CRAN or
> Bioconductor. Taken one step further we might have a transparent
> wrapper to quickly install any version of a package even if it is not
> yet part of Guix.
>
> This might work like this:
>
> * user issues “guix package --install --via cran gdtools@0.0.3”
>
> * Guix runs the CRAN importe to recursively generate package expressions
> for “gdtools” at the given version. The package does not have to
> exist in Guix yet. The generated package expressions are cached
> somewhere (e.g. ~/.cache/guix/…genomation…).
>
> * Guix loads the newly imported package expressions from
> ~/.cache/guix/…genomation… and tries to build them.
>
> * Optionally, users can take the imported expressions, clean them up and
> send them as patches to us :)
>
> This obviously depends on the quality of the importers, but I think it
> wouldn’t take much effort to make this a reality.
Could this approach also support earlier R versions? Reasons one would
want this:
- one comes back to a project after sebatical. Because new R versions
have been installed the analysis gives different results and/or is
broken.
- one needs to re-run an analysis to reproduce a result or to do
sensitivity studies.
In such cases it is far preferable, but usually problematic, to
reconstruct the environment in which the anaysis was run. If guix could
be used to do this, it would be a compelling argument for adoption in a
research lab situation.
> The main problem with offering magic like this is that it must be
> reliable or else it would just be frustrating users.
Agreed. But any experienced R user knows that package installation can
be a drama. So it does not have to be perfect to match or exceed user
expectaions. If the user's alternatives are ...
1) wait for sysadmin to do it
2) give this a shot
... most users will happily try pushing this button ;-)
- George
next prev parent reply other threads:[~2016-08-01 21:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 14:36 [PATCH] gnu: r: Update to 3.3.1 Roel Janssen
2016-07-30 19:41 ` myglc2
2016-07-30 22:55 ` Ludovic Courtès
2016-07-31 16:47 ` myglc2
2016-07-31 4:09 ` Pjotr Prins
2016-07-31 9:45 ` Roel Janssen
2016-07-31 17:49 ` myglc2
2016-08-01 6:00 ` Pjotr Prins
2016-08-01 17:17 ` myglc2
2016-08-01 19:44 ` Roel Janssen
2016-08-01 20:14 ` myglc2
2016-08-02 8:31 ` Roel Janssen
2016-08-01 20:02 ` Ricardo Wurmus
2016-08-01 20:59 ` myglc2 [this message]
2016-08-02 6:00 ` Ricardo Wurmus
2016-08-01 21:20 ` Ludovic Courtès
2016-08-02 3:50 ` Pjotr Prins
2016-08-02 5:53 ` Ricardo Wurmus
2016-07-31 17:12 ` myglc2
2016-07-31 17:34 ` Roel Janssen
2016-07-31 8:04 ` Andreas Enge
2016-08-01 8:26 ` 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
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=86wpk0gq8w.fsf@gmail.com \
--to=myglc2@gmail.com \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).