2018-01-01 20:33 GMT+01:00 Tollef Fog Heen <tfh...@err.no>: > ]] Vincent Bernat > > > ❦ 1 janvier 2018 17:47 +0100, Jonas Smedegaard <jo...@jones.dk> : > > > > > Purpose of the Standards-Version field is *not* to keep you busy > > > silencing corresponding lintian warning, but to state which version of > > > Debian Policy the package is verified to comply with. > > > > And why is it useful to know something like that? > > Because you can then you can focus on the particular changes from > when-last-synced-with-Policy rather than checking the entirety of the > package against all of Policy. > > > If we don't comply with the latest policy, this is considered a > > serious bug. > > No, it's not. Not complying with policy is anything from wishlist to > critical all depending. > > > We would spare a lot of developer time by not using this field > > anymore. > > I don't think so, I think we save quite a bit of effort by having it due > to the aforementioned reasons. >
About sparing time, having to maintain debian/compat Build-Depends debhelper Standards-Version is overkill. Sure, i suppose there are times it's useful to be decoupled, but wouldn't it be simpler to couple debhelper dependency to Standards-Version ? Jérémy
