Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.slackware    |    I think its the one without Selinux crap    |    87,272 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 86,811 of 87,272    |
|    John Forkosh to All    |
|    upgrade package and any needed libraries    |
|    03 Nov 24 00:16:49    |
      From: forkosh@domain.com              How do you use slackpkg to upgrade a package along with       any libraries that the upgraded package may also need?        In particular, I have a three-year-old -current64       from November 2021 installed, which is using firefox 91.3.       But now, when started, firefox says some features may stop       working January 15, 2025, and "volunteers" to upgrade for me.        But I'm concerned that the upgraded firefox may also       need some libraries upgraded, and that it won't work if       I just let mozilla automatically upgrade firefox for me.       But I'm also not seeing how to identify and upgrade       any such needed libraries with slackpkg (and haven't       been able to google -options to do that).               And finally, if I identify and upgrade those libraries       along with firefox, what about any other older installed       packages that still need the older libraries? Is there       a way to keep both the newer libraries for firefox,       and the older versions for everything else?        From what very little I know, the installed libraries       are usually "addressed" by symlinks library-->library.version,       so both old and new libraries could co-exist, but programs       using them would only see the version pointed to by the       symlink. Is that right? How could I deal with that?       Thanks.       --       John Forkosh              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca