Hi

After reading the docs regarding slackpkg and it's relationship with the changelogs.txt file
I went through some newbie steps to upgrade packages and the kernel in current. I was going to install the Alpha version of 15 but decided to stay with current as it seems to be progressing towards 15 anyway.

I'm not that familiar with how glibc interacts with apps being installed; only know that it has been described as something to be careful of when upgrading apps or a kernel.

I've also seen it being updated in the current changelogs.txt file - I think more than once in the last little while.

My question is - if I keep using current and glibc changes in the future - all the apps that I have previously installed from Slackbuilds will still work when glibc is upgraded - correct?

I mean, if I build a bunch of slackbuild apps with a slightly older glibc but still fairly recent, the slackbuild packages should still for the most part install ok (on a different computer) when a newer glibc gets installs for current - correct?

Maybe I should go back to the Slackware docs to see if there is some information about this eh?

Thanks

A package built against older glibc libraries will keep working when you install newer versions of glibc, no worries.
The other way round will result in failure.
Distro packagers who target multiple distro releases with a single binary package will build these binaries against the oldest of the glibc libraries that's available across these releases.

As for your "Alpha version of 15" - there is no such thing. It's still Slackware-current. Slackware's alpha and beta tags are cosmetic, markers in ChangeLog.txt entries, but there's not actually a permanent release for any of these tags. There was Slackware 14.2. There will be Slackware 15.0. Everything inbetween is Slackware-current.

2 members found this post helpful.

Awesome,

So the question would be - why bother updating glibc? What would force my hand to do that!

Edit: Ok, I get it - build with the lowest glibc and upgrade glibc whenever you can is the way to go.

Thanks Alien Bob!

[QUOTE=firefli;6232479]Awesome,

So the question would be - why bother updating glibc? What would force my hand to do that!I think you will have to read a bit more to get a proper understanding. Your statements do not make sense, perhaps you are interpreting my reply incorrectly.

Hi

Pretty sure I did get what you meant but I should have explained myself better.

What I meant after thinking about what you said was build with an old version of glibc on a virtual machine dedicated to making slackbuilds so that any other computer I installed would have a newer version of glibc and therefore would be ok to easily install those slackbuild packages built with the vm.

Thanks for clarifying...

:-)