From: sashaa@disroot.org   
      
   On Sun, 3 Nov 2024 18:43:09 -0000 (UTC), John Forkosh wrote:   
      
   > Sam  wrote:   
   >> John Forkosh writes:   
   >>   
   >>> How do you use slackpkg to upgrade a package along with any libraries   
   >>> that the upgraded package may also need?   
   >>   
   >> I'm not aware of any Slackware tool for this. I think that this is   
   >> Slackware's biggest technical disadvantage: lack of package dependency   
   >> tracking. Both dpkg and rpm handle that automatically. dpkg and rpm   
   >> were doing everything that you described in your post, for a couple of   
   >> decades now?   
   >>   
   >> Slackware simply does not have any kind of inherent dependency tracking   
   >> between packages. The usual response when this gets pointed out is:   
   >> well, Slackware installs everything in one fell swoop so this isn't   
   >> needed. And this is true: as long as you only need to run what's   
   >> packaged by Slackware,   
   >> you don't need this kind of dependency tracking. If you need to be   
   >> based on a distribution that you can customize with custom or updated   
   >> packages, without everything falling apart, you'll need to look   
   >> elsewhere.   
   >   
   > Thanks for the additional information, Sam. Too bad. I'd of thunk that   
   > PV and other slack maintainers could've migrated these kinds of   
   > capabilities from other linux distros without too much trouble. Maybe   
   > slack16. Anyway, I'm otherwise usually very happy with slack,   
   > so am not yet tempted to "look elsewhere".   
      
   You can actually use Salix's dependency resolution in Slackware. You have   
   to install slapt-get and point it to one of Salix's mirrors of the   
   slackware-15.0/ folder, which has an extra "deps" folder. Then you get   
   dependency resolution for all the standard Slackware packages.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)