On Tue, Feb 02, 2021 at 01:55:19PM +0000, Jelmer Vernooij wrote:
> One of the things that I've been wondering about is whether it would make
> sense to have a configuration file in Debian packages that allows
> maintainers to specify preferences for contributions.
>...
What kind of contributions exactly are you referring to?
For team-maintained packages, I would expect the team to communicate the
rules when accepting a new team member.
For one-time contributions like patches or NMUs the general policy has
always been to try to keep the changes reasonably small.
> lintian-brush has its own configuration file
> (debian/lintian-brush.conf) that carries some of these preferences -
> but they're not really specific to lintian-brush. Ideally this is
> something that we can standardize on (DEP?) and that is honored by
> various tools and services.
>...
I would rather say it would be a problem if we end up having many
tools editing the same files.
> * What Debian/Ubuntu release to stay compatible with,
> to ease backporting. ("compat-release" in lintian-brush.conf)
>...
A debhelper compat bump is a breaking change that must not be done
without the maintainer verifying that it didn't introduce any
regression.
This is the whole point of compat levels.
Unfortunately there is a lack of recognition how many bugs are
introduced by blindly updating debhelper compat levels - staying
at a deprecated compat level is better than a not properly tested
compat bump.
> Cheers,
>
> Jelmer
cu
Adrian
