On Mon, Sep 06, 2021 at 01:44:31PM -0700, Felix Lechner wrote: > On Mon, Sep 6, 2021 at 12:56 PM Jelmer Vernooij <jelmer@debian.org> wrote: > > it would simply be a list of > > known bad values > > I am not sure I agree with the hardcoding of those values unless they > create legal issues like license violations or the risk of criminal > prosecution. How about we repurpose the classification tag > 'upstream-metadata-field-present' to also provide the field contents, > which is what you are after? > > You could then use Lintian's query interface to examine the values to > your liking. That will mean maintainers need to decide which values are valid and which ones aren't. It won't provide maintainers of packages that use invalid settings that they are. Isn't that purpose of lintian? Or, looking at a counter-example - there is e.g. a pypi-homepage tag; not just a homepage classification. Cheers, Jelmer -- Jelmer Vernooij <jelmer@jelmer.uk> PGP Key: https://www.jelmer.uk/D729A457.asc
Attachment:
signature.asc
Description: PGP signature