Re: 2.2.2 changes
> > > Can you explain _why_ you are making this change?
> > > Or is it too complicated ;)
> >
> > interoperability really. Currently we don't use /usr/share/config which
> > KDE defaults to for configuration files...instead we go with /etc/kde2 to
> > follow FHS and Debian policy and we provide a /etc/kderc file to tell KDE
> > about it since the core system doesn't like things outside of it's $(prefix).
>
> Did you find out why? Is it a s/// that does not work for kde_config outside
> $(prefix) or is $(prefix)/config hardcoded?
Stephan explained it to me at one point in time but I don't remember. His
solution was the /etc/kderc file. :)
> > This is all fine and dandy except when we start looking at kde3. I don't
> > want to hose up configuration files or other things when we start doing
> > things with kde3. So this allows for us to do away with /etc/kderc and
>
> Great! I hate the /etc/kderc ;)
>
> > just provide a hardcoded (since it's with KDE's $(prefix)) per release
> > config dir. /usr/share/kde2/config would be a link to /etc/kde2 and
> > /usr/share/kde3/config would be a link to /etc/kde3 and thus we can tell
> > kde apps about config settings without having a confliction between what
> > kde3 uses and what kde2 uses.
>
> Hmm, are you sure that .../kde{2,3}/config works together?
> AFAIU there the kded(?) daemon that scan/caches config stuff during session login.
> So a KDE3 syscoca would ignore system/user config files in .../kde2/config.
> KDE 2 apps saving config changes would write to kde2/config. Restarting the
> app and it looks like the changes are forgotten.
>
> While I like to get rid of /etc/kderc I don't beleave that kde{2,3}/config
> is worth the possible trouble.
if it doesn't work (which I'm still testing) then I'll go with /usr/share/kde/config
and and leave it like that...either way I'm getting rid of /etc/kderc
Ivan
--
----------------
Ivan E. Moore II
rkrusty@tdyc.com
http://snowcrash.tdyc.com
GPG KeyID=90BCE0DD
GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Reply to: