Hi Stefan,
it took me a while to reply to your original message, because I didn’t know what hwdb was supposed to mean. The code snippet in this mail made it clearer to me. > 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. But let’s take a step back: is it possible to provide this hwdb with the udev-service? If not, perhaps we should augment the udev-service to not only accept udev rules, but also custom hwdb files. -- Ricardo
