Gconf glitch



This is a minor conflict :

Both Gconf1 and GConf2 creates a symlink $bindir/gconftool to respective
real binary, namely gconftool-1 and gconftool-2. Is the usage of gconftool
untrustworthy now, and any package dependent on GConf2 should call or run
gconftool-2 instead?

Abel





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]