From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xkeyboard-config overwrote files in CONFIG_PROTECT-ed directory (/usr/share/X11/xkb/symbols)
Date: Sun, 27 Jul 2025 18:40:50 +0300 [thread overview]
Message-ID: <CA+t6X7cs8BEYOgmQAUass8VBr1q2Cvw655SCsFRJH=XbGTNSXA@mail.gmail.com> (raw)
In-Reply-To: <e5aba579-52c0-bb91-3575-86eb6f1b2053@gmail.com>
вс, 27 июл. 2025 г. в 18:33, Dale <rdalek1967@gmail.com>:
>
> gevisz wrote:
> > Ionen Wolkens replied that it should be /etc/xkb/symbols/ directory.
> > I will try it. If it does not work, I will copy my custom keyboard
> > configuration files from there manually.
>
>
> Given the source for the info posted by Ionen, I'd go with that. It
> should apply to Gentoo. Some of the info I found may apply to other
> distros and not so much to Gentoo. As Ionen pointed out tho, it isn't
> well documented which explains why the info is hard to find.
>
> I might add, most all config files in /usr are the default and will
> likely be overwritten. Custom config files should almost always either
> be somewhere in /home if for a user or in /etc if system wide. As far
> as I know, it has always been that way. So, if you have other custom
> config files in /usr, I'd either make sure I have backup copies or find
> out where they should be located to prevent being overwritten.
No, I don't have any other custom config files in /usr.
The problem, however, lies in that that the same custom keyboard
layout files placed in /usr/share/X11/xkb/symbols/ have been preserved
by portage at least for the last 8 years, until 25.07.2025. :(
> I'm not much but glad to have helped. :-D
Yes it helped, thank you.
> Dale
>
> :-) :-)
>
next prev parent reply other threads:[~2025-07-27 15:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-27 12:18 [gentoo-user] xkeyboard-config overwrote files in CONFIG_PROTECT-ed directory (/usr/share/X11/xkb/symbols) gevisz
2025-07-27 13:02 ` Michael
2025-07-27 13:39 ` gevisz
2025-07-27 13:06 ` Dale
2025-07-27 13:24 ` Dale
2025-07-27 13:41 ` gevisz
2025-07-27 14:47 ` Dale
2025-07-27 15:01 ` gevisz
2025-07-27 15:24 ` gevisz
2025-07-27 15:32 ` Dale
2025-07-27 15:40 ` gevisz [this message]
2025-07-27 23:57 ` gevisz
2025-07-28 0:35 ` James Cloos
2025-07-28 0:44 ` Dale
2025-07-28 0:37 ` Dale
2025-07-28 0:41 ` James Cloos
2025-07-28 0:50 ` James Cloos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+t6X7cs8BEYOgmQAUass8VBr1q2Cvw655SCsFRJH=XbGTNSXA@mail.gmail.com' \
--to=gevisz@gmail.com \
--cc=gentoo-user@lists.gentoo.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