From: Pjotr Prins <pjotr.public12@thebird.nl>
To: myglc2 <myglc2@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: r: Update to 3.3.1.
Date: Sun, 31 Jul 2016 06:09:56 +0200 [thread overview]
Message-ID: <20160731040956.GA22271@thebird.nl> (raw)
In-Reply-To: <8660rmgbgh.fsf@gmail.com>
On Sat, Jul 30, 2016 at 03:41:50PM -0400, myglc2 wrote:
> The workaround used by sysops where I work (hospital research lab) is to
> give notice of R upgrades and to make previous releases available for
> reference by ongoing projects. IMO, we should consider how the guix R
> recipe(s) might support a pattern of use like this.
>
> I can assure you that if our users do guix pull and invisibly get a new
> R release, their analyses will from time to time break. So we may want a
> simple way for them to back down to a previous release. So.. I am
> thinking it would make sense to keep previous versions of R in the
> recipe. What do others think?
Hi George,
If bioconductor tests pass on a new R build they *should* work. Guix
is not the same mess that Debian and Fedora are.
Note, meanwhile, that a new R install does not remove the old packages
automatically. One way to work older versions is by using guix
profiles effectively. We introduced Unix modules with Guix, so a
module would point to a well tested and working profile. Just make
sure it does not get GC'd at some point.
Another way to work it is by using a checked out Guix source tree.
That is what we do for Genenetwork deployment. Guix 'pull' simply
represents a version of the source tree - with its combination of
packages. You can force a combination of package versions by keeping
track of your own tree. See
https://github.com/genenetwork/genenetwork2/blob/master/doc/README.org
In the near future I hope we get a version of guix pull which can
essentially achieve the same (i.e. a checked out version of the tree).
guix pull HASH-tag
Pj.
next prev parent reply other threads:[~2016-07-31 4:10 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 [this message]
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
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=20160731040956.GA22271@thebird.nl \
--to=pjotr.public12@thebird.nl \
--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.