Hi, On Fri, 24 Jan 2025, Jonathan Dowland wrote: > To some extent this is backwards. DEPs are supposed to codify best practice; > DEP-14 suggests something that the majority of packages are not actually > doing.
That's not correct. We have this requirement for Debian policy, it's supposed to codify best practices that have been already widely deployed, but not for DEP. DEP are "Debian Enhancement Proposals" so they imply that there are changes to do and the process is there to build some sort of rough consensus about those improvements and build a way forward. > Its status as DRAFT, and the fact it could change at any time, aren't > encouraging etiher. It has been CANDIDATE (not DRAFT) without major changes for a long time. > If a large packaging team adopted it, or the git-buildpackage maintainers > changed their defaults, that would help the numbers. There are large teams that adopted it. But I agree that the fact that git-buildpackage was not updated accordingly is the main reason why we are having this discussion today. And it's a pity because the git-buildpackage maintainer was in favor but simply didn't had the time to handle that transition properly, and nobody else did it either (me included). AFAIK Otto started to contribute to git-buildpackage for this, so hopefully that will change now. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
