From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Stefan Huchler <stefan.huchler@mail.de>
Cc: help-guix@gnu.org
Subject: Re: define udev-service-type fails with "did you forget to import.." error
Date: Sun, 04 Oct 2020 17:00:24 +0200 [thread overview]
Message-ID: <87imbq9gtz.fsf@nckx> (raw)
In-Reply-To: <87pn5y13d6.fsf@mail.de>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Stefan,
Stefan Huchler 写道：
> When I try to redefine the udev-service like described in [0]
[...]
> I get following error: /etc/config.scm: [...]
That's not what [0] describes, is it? It illustrates some service
concepts, using real code as example.
It doesn't imply that the example code can or should be added to a
system configuration.
>> That module does not export udev-shepherd-service AFAICT.
> And which does,
Nobody: (gnu services base) defines udev-shepherd-service but does
not export it. It's not intended to be API, nor do I think it
needs to be.
You might be able to use (@@ (gnu services base)
udev-shepherd-service), which forces the module to give up its
secrets. It's not good style, and it won't always work but often
does.
> and why does guix cli interface claim it would do that,
> with it's hint?
Because it's naive. See <http://issues.guix.gnu.org/43498> and -
please! - beat me to a fix ;-)
Kind regards,
T G-R
[0]:
https://guix.gnu.org/manual/en/html_node/Service-Types-and-Services.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-04 15:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 21:23 define udev-service-type fails with "did you forget to import.." error Stefan Huchler
2020-09-29 14:12 ` Ludovic Courtès
2020-09-29 16:23 ` Stefan Huchler
2020-10-04 10:29 ` Ricardo Wurmus
2020-10-04 14:18 ` Stefan Huchler
2020-10-04 15:00 ` Tobias Geerinckx-Rice [this message]
2020-10-04 20:06 ` Stefan Huchler
2020-10-04 20:25 ` Stefan Huchler
2020-10-04 20:55 ` Tobias Geerinckx-Rice
2020-10-04 10:18 ` Stefan Huchler
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=87imbq9gtz.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=stefan.huchler@mail.de \
/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.
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).