[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: What’s next?
Re: What’s next?
Thu, 08 Jun 2017 16:35:55 +0200
mu4e 0.9.18; emacs 25.2.1
Ludovic Courtès <address@hidden> writes:
> 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.?
That’s not a bad idea! It sure beats messing with a single link and it
makes it possible to more easily manage different versions of Guix.
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
- Re: What’s next?, Maxim Cournoyer, 2017/06/03
- Re: What’s next?,
Ricardo Wurmus <=