From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34902@debbugs.gnu.org
Subject: bug#34902: guix cannot find a module on boot
Date: Thu, 4 Apr 2019 22:42:17 +0200 [thread overview]
Message-ID: <20190404224217.5ddd00f7@scratchpost.org> (raw)
In-Reply-To: <87wokq4ptt.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
Maybe I'm too paranoid but can we have "guix" in the file name "modules.name"
somewhere? Otherwise I see it coming that upstream uses modules.name for an
incompatible purpose and then we'd be with a guix interface that's broken
and/or break their interface.
(So much complexity for something so silly. Honestly, I feel like E-mailing
the upstream author and telling him what I think. WTF :P)
Should we warn when we use the fallback? I like the defensive programming
but I feel we shouldn't have it *silently* fall back when the database is
broken/missing.
Otherwise LGTM!
>(basename file ".ko")
^^^^^^
Nice. Where was that all my life. ;-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-04-04 20:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 9:17 bug#34902: guix cannot find a module on boot Julien Lepiller
2019-03-18 20:42 ` Ludovic Courtès
2019-03-18 21:34 ` Julien Lepiller
2019-03-18 22:40 ` Danny Milosavljevic
2019-03-22 20:27 ` Ludovic Courtès
2019-04-04 20:42 ` Danny Milosavljevic [this message]
2019-08-16 21:10 ` Ludovic Courtès
2019-08-01 9:49 ` bug#34902: Guix " Julien Lepiller
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=20190404224217.5ddd00f7@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=34902@debbugs.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).