From: noisycoil@debian.org 
  
 On 20/09/25 18:37, Jonas Smedegaard wrote: 
 > What is sensible to me is to enable optimization by default and support 
 > DEB_BUILD_OTIONS=noopt. Then it is clearly visible to Debian developers 
 > when a package apply some tradeoff. 
  
 We're talking about policy, so we don't really care about non-default 
 DEB_BUILD_OPTIONS in this context. Honoring them is nice if someone 
 wants to deviate, but that's not the point being discussed. Always-on 
 optimization, in the context of policy, amounts to no tradeoff. This is 
 a valid point of view of course, but we should recognize it for what it is. 
  
 > What I commonly do currently as tradeoff with autopkgtest is to check 
 > default feature set on all architectures, and no-features and each 
 > feature only on amd64 - declared explicitly in debian/tests/control, 
 > and can be extended to prepend DEB_BUILD_OTIONS=noopt to some tests as 
 > needed. 
  
 This is a hard no as far as I'm concerned. Not testing release 
 architectures is not acceptable for me, especially since it's not 
 uncommon to catch architecture-related bugs in autopkgtests. I'm also 
 biased in this, since I don't use amd64. 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)