On Wed, May 27, 2009 at 3:23 PM, Pavol Rusnak
Sankar P wrote:
On Wed, May 27, 2009 at 3:08 PM, Pavol Rusnak
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.
Ah. That could be tricky. Some packages are packaged differently across distributions. For instance, last time I checked, evolution was packaging a /usr/bin/evolution.bin binary which had some hacks to pre-load to some Samba of evolution's own, instead of relying on system samba (for its MAPI provider etc.) However, it has been a long time and things could've changed/improved now. -- Sankar P http://psankar.blogspot.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org