From: Thomas Danckaert <post@thomasdanckaert.be>
To: guix-devel@gnu.org
Subject: Re: guix system delete-generations -- advice?
Date: Tue, 14 Feb 2017 21:14:59 +0100 (CET) [thread overview]
Message-ID: <20170214.211459.2192004068693078941.post@thomasdanckaert.be> (raw)
In-Reply-To: <20170214.210445.1695511664334184525.post@thomasdanckaert.be>
(I somehow messed up the encoding/body of previous message, so here it
is again. my apologies)
I added `guix system delete-generations' in my git checkout, WIP patch
attached. I had started to adapt the corresponding code from `guix
package delete-generations', but then realized that
`delete-matching-generations` from (guix scripts package) contains
everything that's needed (could it be moved to (guix ui)?).
One thing I'm not satisfied with is this: `reinstall-grub' does not
reproduce custom grub menu entries added in the (grub-configuration)
section of a system's bootloader configuration. So users with a
dual-boot system lose theire non-GuixSD grub entries after running
“guix system delete-generations” (until they run “guix system
reconfigure” again). The existing “guix system switch-generation” has
the same problem.
Is there a way to retrieve the current custom grub entries, other than
providing a system configuration, or, I hardly dare say it out loud,
parsing grub.cfg? How could this be improved?
cheers, Thomas
ps I also noticed that passing an empty string ("") as a command line
argument to many guix commands returns a guile backtrace, e.g. guix
system list-generations "". I find this a little messy, or is it a
feature?
next prev parent reply other threads:[~2017-02-14 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 20:04 guix system delete-generations -- advice? Thomas Danckaert
2017-02-14 20:14 ` Thomas Danckaert [this message]
2017-03-07 14:42 ` Ludovic Courtès
2017-03-07 16:53 ` Thomas Danckaert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170214.211459.2192004068693078941.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.