Experimental and lowering to pedantic are orthogonal flags.  I think both
should be done, as removing --as-needed has very marginal relevance so it
can't possibly be labeled as "warning".  But due to what Christian said
(which matches my thoughts) I likewise believe the tag should be hidden for
the time being. I
 agree that marking the tag as experimental should be enough. I reckon not
many display experimental tags, since those are hidden behind a flag that
kind of discourage its usage.

Perhaps also consider adding a note in the description that suitability of
the change needs to be considerated if the package will be subject of
backporting (whilst it's true that there is a risk of overlinking, many of
those are not that severe: think of a Qt application that links a a bunch
of Qt library just because upstream cargo-culted a list in a qmake file,
even when not using all of it.  An extra link to a QtSvg that is not used
won't bother anybody.  But there are more severe cases.). Such note should
clearly mention that this is safe only if the package won't target anything
lower than bullseye, so that it can stay also during the bookwork cycle for
people considering oldstable-bpo uploads.

Lastly, I am not sure if this works for your development workflow, place a
code comment todo to drop the experimental flag once bullseye is out.

Thank you for your tireless work on lintian!

On Tue, 5 May 2020, 2:50 pm Christian Kastner, <c...@debian.org> wrote:

> On 2020-05-05 13:58, Chris Lamb wrote:
> > I would like to do a Lintian release today, so given that a) I was led
> > to believe skipping the tag for backports uploads would be sufficient
> > and b) that I would not like to leave the resolution of this bug for
> > another release, I would like to make the concrete proposal that we
> > remove this tag (or possibly, mark it as pedantic, experimental, and
> > add a suitable note to the long description). Would you concur?
>
> By my gut, either marking it as experimental, or removing it and
> re-adding it once bullseye becomes stable, are superior approaches to
> marking it pedantic. Pedantic might still motivate, well, a pedant, to
> change something.
>
> Generally speaking, I found the tag informative, because I wasn't aware
> of this new default setting in bullseye until lintian pointed this out
> to me. It's just that a warning is a strong call to action.
>
> Christian
>

Reply via email to