Summary: | ._cfg000_* files in /usr/share/X11/xkb, while CONFIG_PROTECT is set to /etc | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Grygoriy I. Fuchedzhy <grygoriy.fuchedzhy> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alexey.kv, x11 |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Grygoriy I. Fuchedzhy
2010-12-25 15:32:10 UTC
Well, xkeyboard-config ebuild does add the correct path to CONFIG_PROTECT. (In reply to comment #1) > Well, xkeyboard-config ebuild does add the correct path to CONFIG_PROTECT. > Can't see where it does, nothing like CONFIG_PROTECT in ebuild or xorg-2 eclass. Anyway even if it does, that is not correct, because this way user is not notified in any way that he haven't got updates and there are some files to be resolved. By the way, it seems that there is no way to tell to setxkbmap to use custom directory for this files. I mean if I want to add some custom symbols file(which I want to do now) I have to place it into /usr/share/X11/... which is not good at all. Maybe this files should be installed into /etc/X11/xkb/, this will solve issue with CONFIG_PROTECT and will not force users to modify any files in /usr/... It seems that all you have to do for this is to add --with-xkb-config-root= configure option to setxkbmap ebuild. (In reply to comment #2) > Can't see where it does, nothing like CONFIG_PROTECT in ebuild or xorg-2 > eclass. I don't see anything like that either (usually it's done via a call to doenvd). You can use a command like this to find out which packages modify CONFIG_PROTECT: portageq owners / $(grep -rl CONFIG_PROTECT /etc/env.d) (In reply to comment #4) > You can use a command like this to find out which packages modify > CONFIG_PROTECT: > portageq owners / $(grep -rl CONFIG_PROTECT /etc/env.d) I looked through files reported by this command, there are several CONFIG_PROTECT_MASK entries, all of them are masking something in /etc/, nothing related to /usr/... (In reply to comment #0) > Yestarday I've upgraded recently stabilized xorg-server and friends. Today I've > accidently found following files on my system: > $ find /usr/share/X11/xkb/ -name '._cfg*' > /usr/share/X11/xkb/._cfg0000_compat.dir Perhaps these files are left over from an obsolete CONFIG_PROTECT setting. Obsolete settings like these can easily hang around in your environment if you forget to source /etc/profile (or re-login/reboot). This is a common problem caused by the /etc/env.d system, as discussed in bug 194043. I see. So this should be probably resolved as a duplicate of bug 194043. I will open another bug regarding installation place and editing of xkb files. Thanks. *** This bug has been marked as a duplicate of bug 194043 *** |