Ludovic Courtès transcribed 2.0K bytes:
> Hello Guix!
>
> l...@gnu.org (Ludovic Courtès) skribis:
>
> > Here’s a series of improvements that I think we should make in ‘guix
> > pull’:
> >
> > • Use Git instead of downloading a whole snapshot every time. The Git
> > checkout would be kept i
Hello Guix!
l...@gnu.org (Ludovic Courtès) skribis:
> Here’s a series of improvements that I think we should make in ‘guix
> pull’:
>
> • Use Git instead of downloading a whole snapshot every time. The Git
> checkout would be kept in ~/.cache/guix/pull/checkouts, say.
That was done a whil
On Wed, Feb 22, 2017 at 07:57:06AM +, Pjotr Prins wrote:
> To keep things simple I propose a channel simply reflects a fixed
> version of a git tree of a Guix package list. I.e., the exact *state*
> of the combined list of packages is what we support in a channel. The
> git checkout can be stor
I wrote up a 'white paper' on a new implementation of Guix channels.
The easy on the eyes version you can read here:
https://github.com/pjotrp/guix-notes/blob/master/proposals/channel.org
* On Channels
Related to debbugs https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22629 and
https://debbug
Hello!
Here’s a series of improvements that I think we should make in ‘guix
pull’:
• Use Git instead of downloading a whole snapshot every time. The Git
checkout would be kept in ~/.cache/guix/pull/checkouts, say.
A related question is whether to use Git itself, which is pretty big
