myglc2 writes:
> Roel Janssen writes:
>
>> myglc2 writes:
>>
>>> Pjotr Prins writes:
>>>
On Sun, Jul 31, 2016 at 01:49:00PM -0400, myglc2 wrote:
> Guix has marvelous raw tools to do anything. The question is how to make
> it simple enough for someone that is basically an R use
myglc2 writes:
> Ricardo Wurmus writes:
>
>> myglc2 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
>
Pjotr Prins writes:
> On Mon, Aug 01, 2016 at 10:02:05PM +0200, Ricardo Wurmus wrote:
>> 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
On Mon, Aug 01, 2016 at 10:02:05PM +0200, Ricardo Wurmus wrote:
> 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.
>
Hi,
Ricardo Wurmus skribis:
> 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.
It’s indeed doable
Ricardo Wurmus writes:
> myglc2 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
Roel Janssen writes:
> myglc2 writes:
>
>> Pjotr Prins writes:
>>
>>> On Sun, Jul 31, 2016 at 01:49:00PM -0400, myglc2 wrote:
>>>
Guix has marvelous raw tools to do anything. The question is how to make
it simple enough for someone that is basically an R user to take
advantage of
myglc2 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
myglc2 writes:
> Pjotr Prins writes:
>
>> On Sun, Jul 31, 2016 at 01:49:00PM -0400, myglc2 wrote:
>>
>>> Guix has marvelous raw tools to do anything. The question is how to make
>>> it simple enough for someone that is basically an R user to take
>>> advantage of them. The challenge in guix R p
Pjotr Prins writes:
> On Sun, Jul 31, 2016 at 01:49:00PM -0400, myglc2 wrote:
>> > I think what you're looking for in your hospital research lab is what
>> > Pjotr describes as a certain check-out of the Guix source tree.
>>
>> But it is not simple to use. It is to technical an approach to appea
Roel Janssen writes:
> Dear Guix,
>
> With the following patch I would like to update R to 3.3.1. I tested
> with R packages I regularly use and everything seems to work just fine.
>
> Is it OK to upgrade?
In principle: yes.
I’ll see if I can make updates to all R packages later, once your
R
On Sun, Jul 31, 2016 at 01:49:00PM -0400, myglc2 wrote:
> > I think what you're looking for in your hospital research lab is what
> > Pjotr describes as a certain check-out of the Guix source tree.
>
> But it is not simple to use. It is to technical an approach to appeal to
> the medical researche
Roel Janssen writes:
>> On Sat, Jul 30, 2016 at 03:41:50PM -0400, myglc2 wrote:
>>> 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..
myglc2 writes:
> Pjotr Prins writes:
>
>> 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 shou
Pjotr Prins writes:
> 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
l...@gnu.org (Ludovic Courtès) writes:
> myglc2 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
> 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
Hello,
On Sat, Jul 30, 2016 at 04:36:22PM +0200, Roel Janssen wrote:
> Is it OK to upgrade?
maybe wait until after the core-updates merge?
Andreas
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 suppor
myglc2 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 thinkin
f8b2f287d26c4a4a9a02a7277dc940ed667 Mon Sep 17 00:00:00 2001
> From: Roel Janssen
> Date: Sat, 30 Jul 2016 16:33:17 +0200
> Subject: [PATCH] gnu: r: Update to 3.3.1.
>
> * gnu/packages/statistics.scm (r): Update to 3.3.1.
> ---
> gnu/packages/statistics.scm | 4 ++--
> 1 fil
sen
Date: Sat, 30 Jul 2016 16:33:17 +0200
Subject: [PATCH] gnu: r: Update to 3.3.1.
* gnu/packages/statistics.scm (r): Update to 3.3.1.
---
gnu/packages/statistics.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/statistics.scm b/gnu/packages/statistics.
22 matches
Mail list logo
