Well, partly: I've been "converting" a RHL 7.3 system to approximately Centos 2.1, so found it necessary to "rpm -Va"
I was more than a little surprised at this: [root@magpie root]# rpm -V seamonkey missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser/content missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser/content/overlays.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser/skin missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/browser/skin/stylesheets.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/communicator missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/communicator/content missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/communicator/content/overlays.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/cookie missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/cookie/content missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/cookie/content/overlays.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/editor missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/editor/content missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/editor/content/overlays.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/global missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/global/content missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/global/content/overlays.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/global/skin missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/global/skin/stylesheets.rdf missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/navigator missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/navigator/content missing /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo/navigator/content/overlays.rdf
etc
Reinstalling the packages did no good:
[root@magpie root]# rpm -q --scripts seamonkey postinstall scriptlet (through /bin/sh): # run ldconfig before regxpcom /sbin/ldconfig >/dev/null 2>/dev/null
if [ -f /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl ]; then /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl fi preuninstall scriptlet (through /bin/sh): # is a final removal? if [ "$1" == "0" ]; then /bin/rm -rf /usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo /bin/rm -f /usr/lib/mozilla-seamonkey-1.0.8/chrome/*.rdf fi postuninstall scriptlet (through /bin/sh): /sbin/ldconfig >/dev/null 2>/dev/null # was this an upgrade? if [ "$1" == "2" ]; then if [ -f /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl ]; then /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl fi fi [root@magpie root]# hm. What does /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl?
Oh, it does
[root@magpie root]# head -20 /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl #!/usr/bin/perl
use File::Path; use File::Copy; use File::Glob ":glob"; use POSIX ":sys_wait_h";
$timeout = 60;
%{ENV}->{"MOZILLA_FIVE_HOME"}="/usr/lib/mozilla-seamonkey-1.0.8"; %{ENV}->{"LD_LIBRARY_PATH"}="/usr/lib/mozilla-seamonkey-1.0.8"; %{ENV}->{"MOZ_DISABLE_GNOME"}="1";
umask 022;
if ( -f "/usr/lib/mozilla-seamonkey-1.0.8/regxpcom" ) { # remove all of the old files rmtree("/usr/lib/mozilla-seamonkey-1.0.8/chrome/overlayinfo"); unlink </usr/lib/mozilla-seamonkey-1.0.8/chrome/*.rdf>; [root@magpie root]#
Why is this?
On Wed, 4 Apr 2007, John wrote:
[root@magpie root]# hm. What does /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl?
Why is this?
reading the whole script, it is regenerating 'chrome' files with only the master instance running, presumeably to prevent wayward children from bollixing the process.
not deleting itself, of course, as the title suggests -- just parts of what are essentially configuration matters, which may need migration as versions and releases change.
-- Russ
R P Herrold wrote:
On Wed, 4 Apr 2007, John wrote:
[root@magpie root]# hm. What does /usr/lib/mozilla-seamonkey-1.0.8/mozilla-rebuild-databases.pl?
Why is this?
reading the whole script, it is regenerating 'chrome' files with only the master instance running, presumeably to prevent wayward children from bollixing the process.
What are these chrome files anyway? When I was young, chrome was the decoration of choice on Yank Tanks.
not deleting itself, of course, as the title suggests -- just parts of what are essentially configuration matters, which may need migration as versions and releases change.
Surely /usr is the wrong place to be doing this? /usr is supposed to be able to be mounted ro (not at this moment, of course) and shared between many machines, virtual or real.
If it's configuration data then it should be in /etc. If it's volatile but not condifuration, then in /var.
Best, is to build the package at build time, not at install time.
And, if those files are not required to be in the package, why the heck are they?