https://bugzilla.novell.com/show_bug.cgi?id=388167 User lrupp@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=388167#c2 Lars Vogdt <lrupp@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lrupp@novell.com Status|RESOLVED |CLOSED --- Comment #2 from Lars Vogdt <lrupp@novell.com> 2008-05-08 05:43:24 MST --- OK: so it's time for me to provide a more functional package outside openSUSE. Because the only other option for the problem above is patching the package manager to execute scripts after each de-/installation or update of a package - this is nothing my time or knowledge permits. Sorry, but your answer looks like "Please reinvent the wheel" - sad to see good things go because somebody overboards the tools in the past. I can't find an easy solution for my problem: 1) boot init scripts => the tool runs via cron. So you tell me I should create a daemon watching rpms database and update the inode database if this changes? 2) %trigger or other %post/%pre scripts only affect the package itself. I need to watch other packages during installation/update. Or do we want to provide an updated rkhunter package with every package update of openSUSE? 3) cron job can be a solution. But this runs even if nothing happend - or (the worst case) would run the database update even if a user and not root has changed something. Which is a security nightmare. So this update should only be done by root - and SuSEconfig can only be called by root. As result root must run a database update per hand after each package installation/remove/update. Wonderful autmated world... As result I drop the package in the official distribution. All your "alternatives" make more work than the "normal" SuSEconfig solution. WONTFIX => drop. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.