[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

What’s the use for Standards-Version?


the question in the subject may sound a bit naive, but I’m starting to
wonder why we still set the Standards-Version in package control files.

AIUI, this header is here to indicate which version of the policy the
package is supposed to conform to. This way, we have a way to enforce
which policy versions are supported, e.g. in a stable release, by
forbidding the too old versions.

However I think this approach doesn’t fit the current way we deal with
policy changes. The de facto way of dealing with policy breakages
currently is to directly report serious bugs against packages not
conforming, regardless of the Standards-Version they declare. We will
even often NMU them without changing the Standards-Version, while having
actually fixed them to conform to newer versions.

Currently I don’t think this header reflects anything useful in a vast
majority of our packages. I’m spending more time updating the header
than actually updating old packages to conform to policy changes.

What would you think of deprecating this header?

 .''`.      Josselin Mouette
: :' :
`. `'   “I recommend you to learn English in hope that you in
  `-     future understand things”  -- Jörg Schilling

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=

Reply to: