Sankar P wrote:
On Wed, May 27, 2009 at 3:08 PM, Pavol Rusnak <prusnak@suse.cz> wrote:
We could patch these wrappers to take care of vacuuming the DB at application exit (or at N-th exit, or storing the date of the last vacuum and check if it's older than N days). What do you think?
Is it okay for multiple rpms to patch a single file ? (I know it is okay for something like /etc/pam.d/gdm) I am not sure if there are any packaging guidelines against such practices.
i.e., our vacuumizer will patch /usr/bin/firefox which is owned by someother package, FireFox.
No. I was suggesting to patch the individual packages, so the vacuumizer wouldn't be needed anymore. And to get these patches upstream.
If it is okay, then patching the wrappers to update on every Nth access may be the smartest fix to speedup things. In this way, you don't have to vacuumize the db-s of applications that you may never use. For instance, if someone is happy with his mutt+fetchmail, he need not worry about a new vacuumizer grinding the disk searching for 'folders.db' under ~/.evolution.
Agree. -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o Package Maintainer Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org