home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   linux.debian.maint.emacsen      Maintaining Emacs on Debian      675 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 121 of 675   
   Sean Whitton to Aymeric Agon-Rambosson   
   Bug#1111856: compat-el: autopkgtest regr   
   02 Sep 25 10:40:01   
   
   XPost: linux.debian.bugs.dist   
   From: spwhitton@spwhitton.name   
      
   Hello,   
      
   On Mon 01 Sep 2025 at 01:09pm +02, Aymeric Agon-Rambosson wrote:   
      
   > Hello everyone,   
   >   
   > Le vendredi 29 août 2025 à 11:31, Sean Whitton  a   
   > écrit :   
   >   
   >> This makes sense to me, but do we know why it was ever useful?   
   >   
   > Some upstream maintainers started pulling it as a dependency, in order to not   
   > have to condition their code to emacs versions, while also using the latest   
   > functions provided by the most recent emacs. This library made sense to them   
   > insofar as it allowed them not to have to update their code down the line.   
   >   
   > Since the upstream maintainers of some third-party elisp libraries started   
   > using it as a dependency, we had to package it to package those libraries as   
   > well.   
   >   
   >> I guess it's only useful when the version of Emacs in Debian is a major   
   >> version behind upstream?  Which is generally only a short lived   
   >> situation?   
   >   
   > Now, since a stub version of compat is included in emacs since version 30,   
   > compat is only going to be useful to us if :   
   > - a new function appears in the 31 branch.   
   > - AND the maintainer of compat decides to implement it, and   release some   
   >  version of compat 31.x.x.x.   
   > - AND some third-party elisp maintainer (of a package we package   in debian)   
   >   decides to pull this compat 31.x.x.x version as   dependency in order to   
   use   
   >  this brand new function.   
   >   
   > If this happens and we have removed compat, we will have to wait for emacs 31   
   > to be released (and packaged by us) to be able to package this new version of   
   > the third party elisp library.   
   >   
   > I am not sure how likely this situation is, and whether this is really a   
   > problem : we could perfectly decide to delay packaging a new version of a   
   > third-party elisp library until after the needed emacs version is released by   
   > upstream and packaged.   
      
   Thanks for the analysis.  I don't think the compat-el maintainers would   
   ever do that, so I still think we should remove compat-el.   
      
   --    
   Sean Whitton   
      
   --=-=-Content-Type: application/pgp-signature; name="signature.asc"   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iQJNBAEBCgA3FiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmi2q3wZHHNwd2hpdHRv   
   bkBzcHdoaXR0b24ubmFtZQAKCRBpW3rkvwZiQJrgD/4qcPuAPSHEU7hish223OpI   
   IPFRvYe9eliQfL0Xwa2ZYCmbzhtA1WCZqdhuRqj7hjgZgowKUudE0Y9G22k71WxU   
   Oad8yA/fqWI14DsS/qN8UO9xoY8ZxMlb1uofbgs9xH+zLa7NGwC8tVJzYXQZzdLL   
   BFoe3eOAnZUOKwy/XLVYscACXNRNf/noDYyaZeudtyvv5t2GwILEvLYq2FLmCudr   
   yH3aJcCdJaX8hHVEvdiT5mGUBYZlXvdpORo/hqTmiu9FaNVt70urmyOm7I3qbGOl   
   JrQSTTF0RhNY8wbQAiJRmMJlEOAAEwJgbbDCc7RKf9kIiNLW/43WRsr39OYxkKa2   
   HGkCZBJpIf02XIyQ4SqCxT1w31/LE6BKng08DTJnuiPsNnx1ujYFaJ3aWcBxO4e3   
   4tgEj/Vs7zArU5ZOD7PIQiR/9oqCL1wGVU56ZC96fKf3mwdldFrayA86TsZXt1CY   
   oSN31u/FDh+b5C62djCmlfn5dTSBf2+k2pXy/H/JPnj/1ZRyBWiICp+XPcT8zhZl   
   WUKbPcEATEGeUNAgSVKJCh4fHN3RY8fW/LDQY9miH9sinU3PfDYnKa5noqSK87D3   
   1vHtkzIXjc/AOa4tYmFmb71Prhw20sNzlu2V6GrUiahoxwGkfgsDbzjP1pfhmVRf   
   dDVB5rRxJSgK4tA8COATsg==Mggv   
   -----END PGP SIGNATURE-----   
      
   --- 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