From: Ricardo Wurmus <rekado@elephly.net>
To: myglc2 <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: r: Update to 3.3.1.
Date: Mon, 01 Aug 2016 22:02:05 +0200 [thread overview]
Message-ID: <874m745kci.fsf@elephly.net> (raw)
In-Reply-To: <86eg68cstn.fsf@gmail.com>
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. The main problem with
offering magic like this is that it must be reliable or else it would
just be frustrating users.
At least for CRAN I think this is feasible. (Bioconductor is a
different beast as versions would need to be given as Bioconductor SVN
revisions, which breaks the package boundaries.)
~~ Ricardo
next prev parent reply other threads:[~2016-08-01 20:02 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 [this message]
2016-08-01 20:59 ` myglc2
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m745kci.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.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.
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.