guix-devel
[Top][All Lists]
Advanced

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

Re: [PATCH] gnu: Add r-edger.


From: Ludovic Courtès
Subject: Re: [PATCH] gnu: Add r-edger.
Date: Mon, 23 May 2016 23:50:47 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Roel Janssen <address@hidden> skribis:

> Efraim Flashner writes:
>
>> On Mon, May 23, 2016 at 09:33:28AM +0200, Ricardo Wurmus wrote:
>>> 
>>> Leo Famulari <address@hidden> writes:

[...]

>>> All previous releases might still be available via SVN, though, so maybe
>>> we can find a way to generalise this and add an SVN origin as a
>>> fallback.  Maybe we should not use the tarballs at all and convert all
>>> of the Bioconductor packages to use SVN instead?
>>> 
>>
>> It would be easier than making our own archive of releases or
>> systematically uploading them all to archive.org.
>
> I've encountered missing tarballs a couple of times now.  I think it would
> make Guix more "complete" to add an option to consistently store source
> tarballs, so they can be backed up somewhere.
>
> We could integrate this with the substitutions infrastructure, or create a
> separate component that works kind of like this:
>
> If could add an option to export source tarballs from the store to a
> custom directory that maintains the structure:
> <dir>/<sha256-hash>-<name>-<version>.<extension>, then we could easily set
> up a web server with <dir> as webroot.

Did you see:

  https://lists.gnu.org/archive/html/guix-devel/2016-05/msg00450.html

?

This should address 404s for people who don’t use substitutes (people
using substitutes don’t have these problems since sources are also
substitutable.)

> This can be completely automated, so I don't think it has to be a lot of
> work:
> 1. guix package --export-source-tarballs=/var/www/public_html/

We could do this, but I figured we might as well let others do it.  :-)
Currently we have tarballs.nixos.org, and I think there’ll be another
one pretty soon.  Hopefully that’ll cover our needs.

Thoughts?

Thanks,
Ludo’.



reply via email to

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