Just saw this on the current README:
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!!

The correct way is not to upgrade that package.

Purpose : Explain why Slackware's aaa_elflibs should not be upgradepkg'd
http://connie.slackware.com/~mozes/docs/aaa_elflibs.txt

Ah, thanks for the clarification everyone! Just wanted to make sure. Thanks again!

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.

@sahko: for the most part, I tend to agree. You know that old saying about squeaky wheels and grease though, right? ;-)

Alrighty, I'll go ahead and install it! But if it blows up, I'll send some rain your way mr. workman!

Hey, I survived the upgrade!

Well, wait until Sunday - I'll have the yard cut by then :-)

I hope the rain holds off too! I have a leaky roof.

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.

Just to learn a little more: What kind of problems did you encounter after upgrading aaa_elflibs?

gargamel

WHAT?

I mean, what else do you want? How about this:

Alternatively, instead of being sarcastic:

Psychologically, "Don't press this button because _____" will tend to work much better than "Don't press this button".

Having said that, it's not beyond the wit of man to google why you shouldn't upgrade aaa_elflibs.

1 members found this post helpful.