On Tue, Sep 11, 2012 at 02:43:12PM +0200, Ludwig Nussel wrote:
Michal Vyskocil wrote:
[...] you don't need to do so - all you need is to have proper systemd generator reads the /etc/ld.conf and /etc/ld.conf.d/* to make the proper .path service
PathChanged=|/usr/lib PathChanged=|/usr/lib64
which will trigger the ldconfig
ExecStart=/sbin/ldconfig
Then, you can freely drop the ldconfig from %post scripts out.
Unless you install a chroot... The proper solution would be IMO a) allow ldconfig to (un-)register individual libraries directly so it doesn't have to scan all directories all the time b) make rpm call ldconfig on individual libraries automatically
Well, then lets deprecate chroot in favor of systemd-nspawn ;-) But seriously - I am not pretty sure if systemd will handle that correctly, but what will happen if we will have the ldconfig-generator and ldconfig.service pulled in as dependencies, will the PID 1 act or not? If not, then unfortunatelly we have the counter-example of the systemd-way ... Regards Michal Vyskocil