From: Stefan Huchler <stefan.huchler@mail.de>
To: help-guix@gnu.org
Subject: Re: how to add hwdb of keyboard
Date: Mon, 14 Sep 2020 23:41:11 +0200 [thread overview]
Message-ID: <87k0wwniiw.fsf@mail.de> (raw)
In-Reply-To: 87tuw3oos1.fsf@mail.de
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?
Stefan Huchler <stefan.huchler@mail.de> writes:
> I build a package for it:
>
> (define-module (x220-hwdb)
> #:use-module (guix packages)
> #:use-module (guix download)
> #:use-module (gnu packages compression)
> #:use-module (guix build-system copy)
> #:use-module (guix licenses))
>
> (define-public x220-hwdb
> (package
> (name "x220-hwdb")
> (version "1.0")
> (source (origin
> (method url-fetch)
> (uri "https://github.com/spiderbit/emacs-ergo-thinkpad-kb-layout/archive/master.zip")
> (sha256
> (base32
> "0rx791b7mq5visa9ckyf7py4lz5ml51hn4mzz4rmlpnlrcds4x8v"))))
> (build-system copy-build-system)
> (inputs `(("unzip" ,unzip)))
> (synopsis "Bla")
> (description "Bla bla bla")
> (home-page "https://www.gnu.org/blablabla")
> (license gpl3+)))
>
> and tried to link it to the expected location:
>
> (service special-files-service-type
> `(("/etc/udev/hwdb.d/90-X220-keyboard.hwdb"
> ,(file-append x220-hwdb "90-X220-keyboard.hwdb"))))
>
> the problem is that the hwdb is compiled but read only, so the file must
> basically be there before the eudev package builds this db.
>
> Is there a better way doing this?
>
> Stefan Huchler <stefan.huchler@mail.de> writes:
>
>> I use a custom keyboard layout on one of my laptops:
>>
>> https://github.com/spiderbit/emacs-ergo-thinkpad-kb-layout
>>
>> I use a hwdb which has the advantage that it works on tty and x11 and
>> that it's keyboard specific so if I connect a external keyboard it does
>> not swap keys on it.
>>
>> I would be ok with giving up the keyboard specific part, I could live
>> with X11 only for a start, but I would like to have it in the config.scm
>> file configured and not only in some home based modifications.
>>
>> Any idea how to do that best in guix, patching a custom my-modified-dvorak
>> keyboard-layout into the xkeyboard-config package maybe?
next prev parent reply other threads:[~2020-09-14 21:46 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 [this message]
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
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=87k0wwniiw.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).