“Delete the generations matching @var{patterns} or ... when omitted.”
Or what actually? I would expect it to delete all the generations but
the current one when PATTERN is omitted, right?
‘--delete-generations’ deletes everything and points the profile to the
zeroth generation. There are
I think we should change ‘--list-generations’ to not output the zeroth
generation. Even though it could be present in the profile, users
shouldn’t be concerned about it.
Agreed.
Good.
I think it should be impossible to remove Generation 0 through the
command-line tools, because that
Hi Alex!
Alex Sassmannshausen alex.sassmannshau...@gmail.com skribis:
It's been a while, but if still desired, here the cosmetic revisions for
the list-packages page.
Of course it’s still desired! :-)
Ludovic Courtès writes:
[...]
As a slight complication, I no longer have access to my
HEAD (caf96debc257dee9ad8b0ea74cc6a8241c30dad4) fails. ‘guix-register.log’:
+ type -P sqlite3
/usr/local/bin/sqlite3
+ echo 'select * from ValidPaths where
path=/nix/store/z4pyj3rbgpqpd3mj0rxpbbpg45hlfcbh-guile-bootstrap-2.0;'
+ sqlite3
I think we should change ‘--list-generations’ to not output the zeroth
generation. Even though it could be present in the profile, users
shouldn’t be concerned about it.
Agreed.
Can I push these patches to ‘master’? Should I document that the zeroth
generation is always ignored?
From
