From: Thomas Danckaert <post@thomasdanckaert.be>
To: ludo@gnu.org
Cc: guix-devel@gnu.org
Subject: Re: guix system delete-generations -- advice?
Date: Tue, 07 Mar 2017 17:53:28 +0100 (CET) [thread overview]
Message-ID: <20170307.175328.195151232620457700.post@thomasdanckaert.be> (raw)
In-Reply-To: <878tohb123.fsf@gnu.org>
From: ludo@gnu.org (Ludovic Courtès)
Subject: Re: guix system delete-generations -- advice?
Date: Tue, 07 Mar 2017 15:42:44 +0100
>> 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.
>> [...]
>> 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?
>
> Very good point, it’s really a shortcoming.
>
> To fix it we could add the extra entries to <boot-parameters> (which
> you can see as /run/current-system/parameters.) See what I mean?
Yes, that should work!
> As for how to proceed, I’m fine either way: we could commit your
> ‘guix
> system delete-generation’ patch first, with the understanding that
> it
> has the bug you describe, and then fix the bug; or we could do it
> the
> other way around.
I'd prefer to fix the bug first. My patch is a bit messy anyway (I
just made (delete-matching-generations) an exported function in (guix
scripts package)), and without the grub fix, it doesn't really
improve things a lot.
> [...]
> Doh! It’s a bug in Guile’s (srfi srfi-37). Could you send it to
> bug-guile@gnu.org?
Done!
Thomas
prev parent reply other threads:[~2017-03-07 16:53 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
2017-03-07 14:42 ` Ludovic Courtès
2017-03-07 16:53 ` Thomas Danckaert [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170307.175328.195151232620457700.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).