Ricardo Wurmus <rek...@elephly.net> skribis: > Chris Marusich <cmmarus...@gmail.com> writes: > >> Leo Famulari <l...@famulari.name> 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’.
