On Fri, May 26, 2000 at 05:17:15PM +0200, Guillaume Cottenceau wrote:
> David Faure <[EMAIL PROTECTED]> writes:
>
> > Well it should be fairly simple in theory: the menu system should only
> > deal with what it knows about, and leave untouched the .kdelnk or .desktop
> > files that come from external packages.
> > The current behaviour, instead, is quite ... aggressive. I suppose
> > this was to make the migration easier (deleting the existing kdelnk/desktop
> > files), but rpm -U could have done that instead, no ?
>
> The problem if we leave the user's files unchanged, is that we come with a
> menu completely screw up. -> entries at the root level, duplicate entries,
> "apps" and "applications" groups, etc..
Because of the files in ~/.kde/share/applnk ?
Ok, the _first_ time, user's files could be removed (or rather backed up),
but once that's done, the user should be allowed to add kdelnks back again,
where he wants to...
And this doesn't apply to 'external' packages, which install into the global
dirs anyway.
--
David FAURE
[EMAIL PROTECTED], [EMAIL PROTECTED]
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today
