Re: menu handling by cdd-common
On Sat, Apr 17, 2004 at 06:57:44PM +0200, Andreas Tille wrote:
> > So a script executing another one is needed.
> > With a symlink it's really simple to check if user changed anything.
> Definitely. But a diff against the old version might do it as well ...
With diff there's no way to distinguish between old script install by
CDD subsystem and script modified by user.
In the first case script should be updated, in the second, script should
be preserved.
MD5 could achieves it in a better way.
If the script matches with a MD5 list, it was instaled by system.
> > The semantic of cdd-update-menus is currently undefined in my mind.
> > The current CVS version is quite old (or probaly not, depending on how
> > it evolves).
> Huh? Old, what is your normal time scale?
Italian time scale, similar to Spanish one, you know :)
Seriously, I meant that I do not know if the current code for
cdd-update-menus is still entirely valid/usefull, with the changes I
explained.
Since the main effort of cdd-update-menus is keep updated system's and
users' menus, and since with the last proposal this effort will be quite
zeroed, most of the code inside the script might be "old":
cdd-update-menus uses several loops inside, probably it could be done in
O(1) at the current state, since there's no more the strong needing to
keep update ~/.menu/cdd-menu.
> I currently do not have any extension to this list. I decided to start
> documenting what you have done. You might have noticed that I checked
> in a cdd-update-menus.8 which is more or less a renamed cdd-install-menus.8
OK, I did not do it waiting for a more stable version of the script.
> which was removed (because cdd-update-menus is much better). If you
In my first view of the problem, the two scripts born really differents
(semantically), currently they're quite the same: install and check.
> would update this man page I would like to start to update the cdd-doc.sgml
> to the current state.
OK. You mean files in doc/common/, don't you?
I created a small README.CDD to summarize something, but it's only
for a quick view and not complete. Quite useless.
I quote what you wrote in a prev. mail:
> ~> update-menus
> Unknown error, message=replacewith($string, $replace, $with): $replace
> and $with must have the same length.
> install-menu: /etc/menu-methods/freedesktop-desktop-entry-spec-dirs:
> aborting
/etc/menu-methods/freedesktop-desktop-entry-spec-apps belongs to
kdelib-bin, probably it's a kde bug, I do not have it installed and
works fine.
thanks to you.
cheers,
c.
Reply to: