From: Stefan Huchler <stefan.huchler@mail.de>
To: help-guix@gnu.org
Subject: Re: define udev-service-type fails with "did you forget to import.." error
Date: Sun, 04 Oct 2020 22:06:55 +0200 [thread overview]
Message-ID: <87eemd21sw.fsf@mail.de> (raw)
In-Reply-To: 87imbq9gtz.fsf@nckx
Tobias Geerinckx-Rice <me@tobias.gr> writes:
> That's not what [0] describes, is it? It illustrates some service
> concepts, using real code as example.
First maybe that is because of text messages and you don't see a face
but your messages sounds a bit passive agressive, but independent from
that I am happy to get a answer, so thanks.
> It doesn't imply that the example code can or should be added to a
> system configuration.
I thought that meaned to be example code to extend such code, but I
english is not my first language and I might read not everything
extremely carefully.
> 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.
Yes and no, I reported 3 weeks ago:
http://issues.guix.gnu.org/issue/43390
So if there would be a direct way to access the hwdb capability of udev
service I would be happy to not use this hack, but for now I priotise
something running over something done the right way, I am good at elisp
but not so good with guile or with understanding the guix architecture,
I try to get a laptop in a usable shape so that I can maybe start being
more productive use the emacs module and well over time learn. I don't
want to become a guix / scheme expert just to get my keyboard working on
my laptop which is my second installation after my netbook on which I
will not code much for guix.
I am totally open to better solutions but if I have to write 10 messages
in 3 weeks I take what I can get, to get the system working.
> 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.
I will test that and report back, thanks for the info.
> Because it's naive. See <http://issues.guix.gnu.org/43498> and -
> please! - beat me to a fix ;-)
Maybe I will, just currently more into some elisp/emacs projects.
Regards
Stefan Huchler
next prev parent reply other threads:[~2020-10-04 20:07 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
2020-10-04 20:06 ` Stefan Huchler [this message]
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=87eemd21sw.fsf@mail.de \
--to=stefan.huchler@mail.de \
--cc=help-guix@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.
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).