From: Ricardo Wurmus <rekado@elephly.net>
To: Stefan Huchler <stefan.huchler@mail.de>
Cc: help-guix@gnu.org
Subject: Re: how to add hwdb of keyboard
Date: Sun, 20 Sep 2020 08:52:33 +0200 [thread overview]
Message-ID: <87h7rtszwu.fsf@elephly.net> (raw)
In-Reply-To: <87bli1o3hl.fsf@mail.de>
Stefan Huchler <stefan.huchler@mail.de> writes:
>>> I forked now the eudev definition to add my hwdb data:
>>>
>>> (add-before 'build-hwdb 'add-my-hwdb-file
>>> (lambda* (#:key outputs #:allow-other-keys)
>>> (let ((out (assoc-ref outputs "out")))
>>> (call-with-output-file
>>> (string-append out "/etc/udev/hwdb.d/90-X220-keyboard.hwdb")
>>> (lambda (port)
>>> (display
>>> "keyboard:dmi:bvn*:bvr*:bd*:svnLENOVO*:pn*:pvrThinkPadX220*\n" port)
>>> (display "KEYBOARD_KEY_7b=compose\n" port)
>>> (display "KEYBOARD_KEY_39=enter\n" port)
>>> (display "KEYBOARD_KEY_79=space\n" port)
>>> (display "KEYBOARD_KEY_70=tab\n" port)
>>> (display "KEYBOARD_KEY_0f=backspace\n" port)
>>> (display "KEYBOARD_KEY_3a=home\n" port)
>>> (display "KEYBOARD_KEY_1c=end\n" port)
>>> (display "KEYBOARD_KEY_0e=backspace\n" port)
>>> (display "KEYBOARD_KEY_7d=backspace\n"
>>> port))))))
>>>
>>> Is there a way to make guix system priotise my modified eudev over the
>>> upstream one?
>>
>> No, you would need to rebuild with your eudev as a replacement.
>
>
> When I try to do that:
>
> (define udev-service-type
> (service-type (name 'udev)
> (extensions
> (list (service-extension shepherd-root-service-type
> udev-shepherd-service)))
> (compose concatenate) ;concatenate the list of rules
> (extend (lambda (config rules)
> (match config
> (($ <udev-configuration> udev initial-rules)
> (udev-configuration
> (udev my-eudev) ;the udev package to use
> (rules initial-rules))))))))
Why not use modify-services? All you want to do is change the
configuration of an existing service, no?
--
Ricardo
next prev parent reply other threads:[~2020-09-20 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 16:47 how to add hwdb of keyboard Stefan Huchler
2020-09-11 23:51 ` Stefan Huchler
2020-09-14 21:41 ` Stefan Huchler
2020-09-14 23:46 ` Ricardo Wurmus
2020-09-15 1:44 ` Stefan Huchler
2020-09-19 21:34 ` Stefan Huchler
2020-09-20 6:51 ` Ricardo Wurmus
2020-09-20 10:28 ` Stefan Huchler
2020-09-20 6:52 ` Ricardo Wurmus [this message]
2020-09-20 10:33 ` 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=87h7rtszwu.fsf@elephly.net \
--to=rekado@elephly.net \
--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).