From: ludo@gnu.org (Ludovic Courtès)
To: swedebugia <swedebugia@riseup.net>
Cc: rekado@elephly.net, 33329@debbugs.gnu.org
Subject: [bug#33329] [PATCH] gnu: Deprecate linux-module shpchp and tell user to remove it.
Date: Sat, 10 Nov 2018 23:31:06 +0100 [thread overview]
Message-ID: <87lg60va39.fsf@gnu.org> (raw)
In-Reply-To: <290b28ec-cd1e-e5e8-275e-133771c7d4f3@riseup.net> (swedebugia's message of "Sat, 10 Nov 2018 13:03:29 +0100")
Hello,
swedebugia <swedebugia@riseup.net> skribis:
> From 4d70dda8c2f119fc6ff9d221eae6f060ff1fcd98 Mon Sep 17 00:00:00 2001
> From: swedebugia <swedebugia@riseup.net>
> Date: Fri, 9 Nov 2018 22:52:12 +0100
> Subject: [PATCH] [V2] gnu: Check for linux-module shpchp and tell user to
> remove it.
>
> * gnu/system/mapped-devices.scm (check-device-initrd-modules): New if
> statement raising a condition if shpchp is found.
I don’t think we should hard-code things like this: they would
accumulate over the years and become unmanageable.
If anything, what should be improved IMO is the error message you get
when specifying a module that is unavailable. That’s not easily done
though since that happens at build time.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2018-11-10 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h8jbang2.fsf@elephly.net>
2018-11-09 22:47 ` [bug#33329] [PATCH] gnu: Deprecate linux-module shpchp and tell user to remove it swedebugia
2018-11-10 12:03 ` swedebugia
2018-11-10 22:31 ` Ludovic Courtès [this message]
2018-11-11 0:15 ` Brett Gilio
2018-11-11 7:27 ` swedebugia
2018-11-11 11:32 ` Ludovic Courtès
2018-11-11 18:42 ` swedebugia
2018-11-12 8:42 ` bug#33329: " Ludovic Courtès
2018-11-11 11:27 ` [bug#33329] " Ludovic Courtès
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=87lg60va39.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33329@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=swedebugia@riseup.net \
/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).