On 11/3/21 23:34, Felix Lechner wrote:
1. Did anyone find the latest Lintian versions (2.109.0 and up) confusing as to whether the :any should be included? The material you would have encountered includes both the context offered by Lintian (the extra information after the tag) and any relevant tag descriptions.
being the one who initially triggered #995981 by blindly following advice of lintian (yes i know: *never* blindly follow lintian's advise), i think i can say that i indeed found the description of the "rules-require-build-prerequisite" tag highly confusing.
in general i think tag descriptions should ony use "machine-parsable advice" if the machine-parsable is meant to be used as-is, and use human language in all other cases. that is: rather than using a string like "python3:any | python3-all:any | python3-dev:any | python3-all-dev:any | dh-sequence-python3" (which looks very much like code) use someting like "the package should probably build depend on one of python3-dev:any or dh-sequence-python3 or [...]".
the point i'm trying to make is not about the correctness of the advice itself, but that an explanation that looks like a code-example is probably going to be understood as such. so if the text is not to be copy and pasted into code, it shouldn't look like tit could.
fmdst IOhannes
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature