Andrey Rakhmatullin <[email protected]> writes: >>> 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.
Indeed -- we made Rules-Requires-Root and Priority:optional irrelevant recently, couldn't we also make Standards-Version an optional field? In many packages, having that field just results in needless churn of debian/ files. /Simon
signature.asc
Description: PGP signature
