all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
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 00:55:32 +0200	[thread overview]
Message-ID: <87oa5e91nf.fsf@gnu.org> (raw)
In-Reply-To: <8660rmgbgh.fsf@gmail.com> (myglc2@gmail.com's message of "Sat, 30 Jul 2016 15:41:50 -0400")

myglc2 <myglc2@gmail.com> skribis:

> I can assure you that if our users do guix pull and invisibly get a new
> R release,

They need to to ‘guix pull’ *and* ‘guix package -u’.

> 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?

I don’t use R myself; keeping a couple of R versions would be fine,
though R packages would always be built only against the latest R.

Ludo’.

  reply	other threads:[~2016-07-30 22:55 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 [this message]
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
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=87oa5e91nf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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.