From: SeerLite <seerlite@nixnet.email>
To: help-guix@gnu.org
Subject: Overriding xkeyboard-config package used by xorg-wrapper
Date: Mon, 1 Nov 2021 16:18:24 -0300 [thread overview]
Message-ID: <a54b0193-44f9-51bd-da63-d96ceb34247b@nixnet.email> (raw)
Hi!
I'm trying to override xkeyboard-config with a fork. I've successfully
defined a variant in my system configuration along with variants for
setxkbmap, xkbcomp and xorg-server that use it as input. They all build
fine and seem to run fine too, but the problem is some things break
unless the new XKB location is set directly in `X`'s `-xkbdir` argument.
I thought it would automatically get set to the correct location if I
used my xorg-server variant in my slim service's xorg-configuration, but
that wasn't the case. I looked at gnu/services/xorg.scm and it seems
like`xorg-wrapper` just uses the default xkeyboard-config for `-xkbdir`.
Is there a way I can make it use the input from the server package I set
in xorg-configuration instead? Or is there at least any way I can
directly override the xkeyboard-config package used by xorg-wrapper?
Thanks :)
SeerLite
reply other threads:[~2021-11-02 21:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=a54b0193-44f9-51bd-da63-d96ceb34247b@nixnet.email \
--to=seerlite@nixnet.email \
--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).