From: Henrik.Carlqvist@deadspam.com   
      
   On Mon, 03 Nov 2025 16:05:30 +1000, noel wrote:   
   > being supported and being "current" (eg: libs wise) are two entirely   
   > different things.   
      
   Yes it is, however in a perfect world, all supported versions of   
   Slackware should get patches for all security holes in libraries and   
   applications. Current will get newer versions of libraries and   
   applications, in a  perfect world those newer versions will be considered   
   stable by upstream providers, but the newer versions might not be   
   backwards compatible with all the configuration files that you have.   
      
   In practice however, supported Slackware stable versions might silently   
   stop providing updates to libraries and applications when upstream   
   providers stop releasing versions on those branches. Even though   
   Slackware usually choose "LTS" versions those "long term support" cycles   
   from the upstream providers might not be as long as the lifetime of a   
   supported Slackware version.   
      
   An example of an upstream provider with rather short release cycles is   
   samba.   
      
   Slackware 15.0 shiped with samba version 4.15.5 which back then was the   
   current stable release of samba. A little more than a month later the   
   4.15 series of Samba went from "latest stable" to "maintenance mode".   
   2022-09-13 the 4.15 series of samba went to "security fixes only" and   
   2023-03-08 the 4.15 series was EOL.   
      
   It seems as if the 4.18 series of samba was rather backwards compatible   
   with 4.15 as it was provided as patches to Slackware 15.0, but the 4.22   
   series of samba has instead been provided in /extra for Slackware 15.0.   
      
   Was it because of some library requirement from PCI DSS that you had to   
   upgrade to current?   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)