guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] gnu: r: Update to 3.3.1.


From: Pjotr Prins
Subject: Re: [PATCH] gnu: r: Update to 3.3.1.
Date: Tue, 2 Aug 2016 05:50:44 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

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.
> 
> This might work like this:
> 
> * user issues “guix package --install --via cran address@hidden
> 
> * 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.)

Another thing to keep in mind is that CRAN has the nasty habit of
moving older source packages to archive directories. Some packages are
removed altogether. We can/should make use of Guix' own source cache.

Pj.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]