>
>
> Has anyone notice that this days almost every rpm has an "ldconfig"
> statement in the scripts. And almost always in both, the postinstall and
> the postuninstal, making it execute twice during a package upgrade.
>
yeh, but have to make sure the new so files are properly registered.
> To make things worse, we now have other things too, like update-menus,
> that are run for every package installed.
>
> Is this really necessary? I mean, in my system (128MB, PPro200, 2x10.1GB
> WD IDE in RAID0) "ldconfig" takes a really long time to run (like 5-10
> mins), making the upgrades of packages a real pain, since it is run at
> least once for almost every package upgraded; and I upgrade packages
> almost every day.
funny thing that it would tkae that long ...it's taking exponential time.
>
> I think this is a real problem for the RPM subsystem, wouldn't it be
> wise to run this only once at the end when installing multiple packages?
> Obviously, some packages (even tough I don't know which ones would) will
> need a current library map to install properly, but I guess most of them
> doesn't. I think this problem should be addressed within RPM itself, and
> not in the individual package scripts or in the distro.
>
then what method do you propose ? you must get ldconfig to run on the system
somehow ...i SUPPOSE one way to address this, would be to
> Any one care to comment about this?
>
> --
> Eugenio Diaz, BSEE/BSCE
> Linux Engineer
> [EMAIL PROTECTED]
>
>
>
