[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What’s next?
From: |
Ludovic Courtès |
Subject: |
Re: What’s next? |
Date: |
Sat, 27 May 2017 12:13:12 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Ricardo Wurmus <address@hidden> skribis:
> Chris Marusich <address@hidden> writes:
>
>> Leo Famulari <address@hidden> writes:
>>
>>> So, I use and recommend `guix pull`!
>>
>> I use it too. Statements by others in this thread that "nobody" uses it
>> or that "everyone" is using Git are mistaken.
>>
>> I use Git when I want to hack on Guix. Otherwise, I use 'guix pull'.
>> IMO, the biggest problem with 'guix pull' is that there is no easy
>> rollback. I can live with long execution times (--fallback is fine, but
>> it'd be nice if substitutes were available more often), and I can live
>> with 'guix pull' causing me to get a version of guix that's broken
>> somehow, but the inability to easily roll back when things go south
>> makes me hesitant to run 'guix pull' regularly.
>
> I believe this can be fixed by adding more links to “.config/guix”,
> i.e. before creating “latest” it would create “2017-05-24:08:21:01.123”
> and then link from there to “latest”. On update it would create a new
> link “2017-05-25:17:45:45.123” and link that to latest. Roll back would
> be a matter of pointing “2017-05-24:08:21:01.123” to “latest”.
There would be some similarity with profiles. Should we simply use
profiles, and effectively turn ~/.config/guix/latest into a profile,
with generations etc.?
Food for thought… :-)
Ludo’.
- Re: What's next?, (continued)
- Re: What???s next?, Maxim Cournoyer, 2017/05/28
- Re: What???s next?, Ricardo Wurmus, 2017/05/28
- Re: What’s next?, Chris Marusich, 2017/05/25
- Re: What’s next?, Leo Famulari, 2017/05/25
- Re: What’s next?, Ricardo Wurmus, 2017/05/25
- Re: What’s next?, Adonay Felipe Nogueira, 2017/05/25
- Re: What’s next?,
Ludovic Courtès <=
- Re: What’s next?, myglc2, 2017/05/29
Re: What’s next?, Ludovic Courtès, 2017/05/27