SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Now, by default, slackpkg blacklists this package. So, my question is, what would be the correct way to upgrade this package? Do I have to drop back into init 1 and do this manually? Thanks ahead of time!!
To expand on that just a bit, and to put all of that together into an answer: :-)
It is safe to upgrade aaa_elflibs *exactly* when the upgraded package hits the tree, because at that point in time, it will contain the same versions of all relevant libraries as what is currently in the tree elsewhere. [1]
If you upgrade it at any point later in the cycle, you run the risk of overwriting one of those same-named libraries that was later upgraded in its corresponding package (e.g. the bzip example in Stuart's document).
[1] If you're upgrading from one stable release (e.g. 12.2) to the next (e.g. 13.0) or to -current (for the first time since installing that stable release), then it should be perfectly safe to upgrade aaa_elflibs at that time.
Since your issue is solved i might as well add my touch.
I don't get the point of the aaa_{elflibs,terminfo} packages, as well as the *-solibs ones.
Maybe they were still needed in 2005 when i assume Slackware was a lot different, especially regarding installation, and the use of floppies.
Nowadays the 1st CD contains all of a/ l/ & n/ so you just end up installing the same files twice and IMO those packages are uneeded.
One might say that aaa_elflibs is a safety net for people doing customized installations, but those people are supposed to know what they're doing in the first place.
I ignored slackpkg's warning and updated it anyway a while back, as I couldn't understand why, and decided to take the risk for a more "up to date" system. And I did encounter problems. Now I know why.
Perhaps the slackpkg people should put a little note in the block list file, to sate potentially dangerous curiosity.
I ignored slackpkg's warning and updated it anyway a while back, as I couldn't understand why, and decided to take the risk for a more "up to date" system. And I did encounter problems. Now I know why.
Perhaps the slackpkg people should put a little note in the block list file, to sate potentially dangerous curiosity.
WHAT?
I mean, what else do you want? How about this:
Code:
--- blacklist.orig 2009-08-15 17:02:05.732282572 -0500
+++ blacklist 2009-08-15 17:02:53.292166938 -0500
@@ -20,7 +20,8 @@
#
# aaa_elflibs can't be updated.
-#
+# "can't" is a contraction meaning "cannot"
+# We don't know how to make it any clearer.
aaa_elflibs
#
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.