Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#5503 - pacman runs ldconfig too many times

Attached to Project: Pacman
Opened by Roberto Braga (Bobonov) - Monday, 02 October 2006, 10:47 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 09 November 2006, 00:32 GMT
Task Type Feature Request
Category
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Basically pacman runs ldconfig each time a lib is upgraded.
It is sufficent to run it once at the end, eventually we need to run it when a lib that is needed during the upgrade is updated, like lib sh depends upon.
It can be achived by adding like a flag to the post install stuff.
Instead of adding /usr/sbin/ldconfig -r to the post install stuff, just a ldconfig= flag can be good.
Like:
ldconfig=0 ---> no need to run
ldconfig=1 ---> run immediately after this package is upgraded
ldconfig=2 ---> run at the end of the upgrade
Pacman should also keep track if it runs ldconfig, I mean if I have 10 pkg with ldconfig=2 but before the end I have a package that has ldconfig=1 therefore I run it, there is no need to run it again at the end.
This will speedup the upgrade especially on older system without RAM.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Monday, 12 February 2007, 09:14 GMT
Reason for closing:  Fixed
Additional comments about closing:  pacman 3 (CVS) no longer behaves this way with ldconfig, and we have more ideal fixes planned for the future
Comment by Erwin Van de Velde (evdvelde) - Monday, 02 October 2006, 10:54 GMT
I like this idea and it could be used for things like fontconfig too...
Comment by Jan de Groot (JGC) - Monday, 02 October 2006, 21:12 GMT
My experience is that pacman only runs ldconfig at the end. Some packages like the gstreamer 0.8 plugins have ldconfig operations in post_install and post_upgrade, for the rest only a few libraries are affected by this.
Comment by Roberto Braga (Bobonov) - Tuesday, 03 October 2006, 10:05 GMT
Yessterday and today I took an eye on htop as tree wiev and I saw pacman calling ldconfig several times (i mean more than 10 only yesterday).
And yesterday most packages were gnome one, so no core lib.
Probably most people doesen't know that pacman call ldconfig at the end anyway and keep on putting it in the post_install script....
Comment by Roman Kyrylych (Romashka) - Sunday, 15 October 2006, 13:11 GMT
http://bugs.archlinux.org/task/3163
http://bugs.archlinux.org/task/3180

Loading...