[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: polkit-kde-kcmmodules editing /usr
From:       David Faure <faure () kde ! org>
Date:       2012-10-30 17:45:29
Message-ID: 30037557.DI23OOFmd1 () asterix ! site
[Download RAW message or body]

On Friday 26 October 2012 17:25:20 Kevin Kofler wrote:
> On Friday 26 October 2012 at 07:00:13, Robby Workman wrote:
> > Good question, and it makes me wonder why we've always just "worked
> > around"
> > it instead of sending patches to do it correctly.  I'm not in a position
> > to
> > look farther into that right now, so I'll just say that it would seem
> > better for KDE stuff to use /usr/share/config/$whatever/ for packaged
> > defaults (IOW, *exactly* what you currently do) with support for
> > overriding those defaults in $sysconfdir/kde/$whatever/
> 
> Yes, and in fact that's how we ship things in Fedora (KDM being a special
> case because it doesn't use KConfig). The KConfig search path in Fedora is:
> 1. ~/.kde/share/config/ – user settings
> 2. /etc/kde/ – systemwide settings
> 3. /usr/share/kde-settings/kde-profile/default/share/config/ – Fedora
> kde-settings 4. /usr/share/config/ – upstream shipped settings
> 
> The way we implement this is that:
> 
> * to implement 3, we ship an /etc/kde4rc (and kderc for legacy kdelibs3
> apps) with the following settings:
> 
> [Directories]
> kioskAdmin=root:
> profileDirsPrefix=/usr/share/kde-settings/kde-profile/
> 
> [Directories-default]
> prefixes=/usr/share/kde-settings/kde-profile/default/
> 
> * to implement 2, we ship a patch to kdelibs:
> http://pkgs.fedoraproject.org/cgit/kdelibs.git/tree/kdelibs-4.6.90-kstandard
> dirs.patch (second hunk, the first one is one of the changes required to
> make LIBEXEC_INSTALL_DIR=/usr/libexec/kde4 work properly)
> The patch is required because we need this to have priority over profiles,
> which isn't supported in the upstream kdelibs code.
> 
> I think the setup we use in Fedora is optimal (and actually I wish all
> configuration systems would work that way, not just KConfig ;-) ).

In KDE Frameworks 5, you'll be able to just export XDG_CONFIG_DIRS to contain
the directories numbered 2, 3, 4 from your list (and XDG_CONFIG_HOME for 
number 1, which moves to ~/.config). Hopefully no custom patch nor global kderc 
required anymore.

-- 
David Faure, faure@kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

[prev in list] [next in list] [prev in thread] [next in thread]