On Fri, Jul 17, 2026 at 03:36:24PM +0300, Martin-Éric Racine wrote:
The problem is that the Debian Policy and debhelper are not alike. In the Debian Policy case, major changes are added whenever, regardless of a specific start of a Debian release cycle. For debhelper, incompatible or breaking changes get accumulated in the next compat level and then released, which makes it easy to sync with a Debian release cycle, and by definition all those changes will be major.Using the Debian release number for the Debian Policy would mean that the first component would no longer imply major changes in the Policy, just the time when they happened in the Debian release cycle.That would be the whole point. The first digit would now have a concrete significance. It would indicate during which Debian release cycle the packaging was last updated.
I think this detail is even less useful than Standards-Version itself as it currently exists. Which problems will this solve?
-- WBR, wRAR
signature.asc
Description: PGP signature
