On Mon, Feb 08, 2010 at 05:37:19PM -0600, Muhammed Uluyol wrote:
So *who* creates the symlink from libfoo.so -> libfoo.so.1.2.3 ? It's either pacman or ldconfig called by pacman. Unless you believe in little gremlins doing it while you sleep.
It is created 'inside' of the package, not during the installation.
$ bsdtar tzf libpng-1.4.0-2-x86_64.pkg.tar.gz .PKGINFO .CHANGELOG usr/ usr/lib/ usr/bin/ usr/share/ usr/include/ usr/include/pngconf.h usr/include/png.h usr/include/libpng14/ usr/include/libpng14/pngconf.h usr/include/libpng14/png.h usr/share/man/ usr/share/licenses/ usr/share/licenses/libpng/ usr/share/licenses/libpng/LICENSE usr/share/man/man3/ usr/share/man/man5/ usr/share/man/man5/png.5.gz usr/share/man/man3/libpngpf.3.gz usr/share/man/man3/libpng.3.gz usr/bin/pnm2png usr/bin/libpng14-config usr/bin/png2pnm usr/bin/libpng-config usr/lib/libpng14.so.14 usr/lib/libpng.so <--- Right there usr/lib/libpng14.a usr/lib/libpng.a usr/lib/libpng14.so.14.0.0 usr/lib/pkgconfig/ usr/lib/libpng14.so usr/lib/pkgconfig/libpng.pc usr/lib/pkgconfig/libpng14.pc
So what ? An update should create/adjust that symlink and it currently does. There's no problem with that. Just don't delete the old *.so, that's all I ask. -- FA O tu, che porte, correndo si ? E guerra e morte !