Gilboa Davara wrote:
On Mon, 2008-05-12 at 21:36 +0530, Rahul Sundaram wrote:
Gilboa Davara wrote:
Look at what the triggers do. What (I think) you need is to know when
the packages reflected in the menus get installed/removed, maybe updated.
Triggers? Do we have DB like triggers in RPM? Please explain.
http://docs.fedoraproject.org/drafts/rpm-guide-en/ch05s03.html
Rahul
Ummm... I'll need to think about it.
As much as I like the idea of auto-magically adding and removing
menu-items, it goes against the very nature of IceWM.
Fast, text-based-configured, super-fast WM.
Seems to me that this approach might be quicker in users' hands - it
might be ready for me seven seconds sooner.
For users' private menus while logged in, there's FAM (File Alteration
Monitor) or its successor to see when you need to reread the file.
The menu created by icewm-xdg-menu looks like it's easily extended to
allow an include to insert/merge a menu from users' home directory. For
sysadmins' sanity, I'd suggest that each include would create a submenu,
not replace or change any existing menu. Any includes would need to be
preserved over a rebuild, but that doesn't look difficult.
- Gilboa
--
Cheers
John
-- spambait
1aaaaaaa@xxxxxxxxxxxxxxxx Z1aaaaaaa@xxxxxxxxxxxxxxxx
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
