From: Henrik.Carlqvist@deadspam.com   
      
   On Thu, 01 Jan 2026 22:47:35 +1000, noel wrote:   
      
   > On Tue, 30 Dec 2025 06:31:01 +0000, Henrik Carlqvist wrote:   
   >> Basically, stable versions of Slackware don't receive any feature   
   >> updates, only security updates and most importantly, those updates are   
   >   
   > Not always the case, as most obvious example is, and I've lost count at   
   > how many times, curl has had updates   
      
   Yes, curl in Slackware 15.0 has been updated from version 7.81.0 to   
   8.16.0, but did any of those versions break any backwards compatibility?   
      
   Another odd example is samba which have rather short life cycles. In   
   Slackware 15.0 samba 4.15.13 was put into /pasture when non backwards   
   compatible 4.18.5 got into /patches.   
      
   These are a few examples of backwards compatibility breaking applications   
   that we are aware of. However, there are also backwards compatibility   
   breaking security updates that are not so obvious. For example, in   
   Slackware 14.2 the last security update of firefox was version 68.12.0 in   
   august 2020. Newer versions of firefox no longer compiled on Slackware   
   14.2. A user Ruari Oedegaard did provide a third party script which   
   downloaded a binary distribution of firefox and repackaged that into a   
   Slackware package. We can easily see security updates that come as   
   patches, but it is not so easy to be aware of security holes which do not   
   receive andy security updates.   
      
   When a Slackware version reaches End Of Life there is a note about that   
   in ChangeLog.txt and we get aware that it will not receive any more   
   security updated. However, long before that, a number of applications   
   usually already has stopped receiving security updates and we are not so   
   aware of that.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)