KConfig and $HOME

Andreas Pakulat apaku at gmx.de
Thu Oct 11 20:58:52 BST 2007


On 11.10.07 15:16:25, Allen Winter wrote:
> On Thursday 11 October 2007 1:12:30 pm Andreas Pakulat wrote:
> > On 11.10.07 12:54:02, Allen Winter wrote:
> > > Does the new KConfig support $HOME in rc files?
> > 
> > Yes and No :(
> > 
> > > I started up korganizer4 from my kde3 desktop and my
> > > standard calendar could not be read.  I think because
> > > KConfig read the wrong file from ~/.kde/share/config/kresources/calendar/stdrc
> > > 
> > > The value it was trying to read was:
> > > CalendarURL=file:$HOME/.kde/share/apps/korganizer/std.ics
> > > 
> > > Looks like KConfig returned the value file://$home/.kde/share/apps/korganizer/std.ics instead.
> > 
> > Right. All KDE3 configs (and pre-KConfig-merge) need to be upgraded and
> > all Entries that have $HOME and are supposed to be expanded need to have
> > [$e] added to the entry key.
> > 
> > The new KConfig only expands $HOME on entries that have this special
> > flag set.
> > 
> Is there no way around this?
> Will kde3 apps work if they see the [$e]?

No

> i.e. once I run KOrganizer4 can I never go back to running KOrganizer3?

That was never supported in KDE, as soon as you let a newer version of a
KDE app write to a config file there's no guarantee it can be read by an
older version. 

Why do you think we all use a different KDEHOME for kde4 ;)

Andreas

-- 
So this is it.  We're going to die.




More information about the kde-core-devel mailing list