Originally Posted by wildwizard
Also the glibc package is designed to not uninstall as it drops the libs in a different directory and then moves them into place, pkgtools simply does not handle those file moves so the package can not be removed.
Okay, so what happens if I don't change glibc versions but re-install it after compiling? Will it replace all the libraries with the ones I recompiled?
What about other library packages; if there's a version update to Glib2, will the old libraries and links be replaced with new ones, or will upgradepkg just ignore them all and install the new ones on the side?
Appreciate the responses.
Compared date of /var/log/packages/packagename with package library file and they match. So old libraries do get replaced when re-installing the same package. The links however, did not get re-created it seems (date was from older package date) though they point to the same file anyway (the actual file is different which is what matters).
I'm going to run a script maybe, from another forum member (grapefruitgirl). It checks for broken links and files that don't belong to any installed package. Think this would be useful for custom Slackware setups; also because upgradepkg doesn't seem to re-create links.
So as everyone pretty much told me, upgradepkg doesn't handle glibc downgrades without borking the system...
Glibc is the most critical library for anything to function (kind of how the kernel is important). Should've known that before blaming upgradepkg. Stupid me!