From: myglc2 <myglc2@gmail.com>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: r: Update to 3.3.1.
Date: Sun, 31 Jul 2016 12:47:14 -0400 [thread overview]
Message-ID: <86h9b5lppp.fsf@gmail.com> (raw)
In-Reply-To: 87oa5e91nf.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) writes:
> 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.
I had forgotten that you are also building many packages. Given that, an
update to the R guix recipe may break some packages. So all the packages
should probably be tested as part of an R recipe update. Do/did we do
that?
As regards keeping a couple of R versions, if we don't keep the
associated packages it will have limited usefulness, so I withdraw
the suggestion.
next prev parent reply other threads:[~2016-07-31 16:49 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 [this message]
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
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=86h9b5lppp.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).