Re: LICENSE values for non-standard OSS licenses

[Jon Turney <jon.turney@dronecode.org.uk>]

On 15/10/2022 13:58, Adam Dinwoodie wrote:
> On Fri, 14 Oct 2022 at 17:28, Jon Turney wrote:
>>
>> On 11/10/2022 09:37, Adam Dinwoodie wrote:
>> [...
>>> ```
>>> ERROR: invalid hints git-filter-repo-2.38.0-1-src.hint
>>> ERROR: package 'git-filter-repo': errors in license expression: ['Unknown license key(s): LicenseRef-inherit-git, LicenseRef-inherit-libgit2, LicenseRef-inherit-libgit2-examples']
>>> ERROR: errors while parsing hints for package 'git-filter-repo'
>>> ERROR: error parsing /sourceware/cygwin-staging/home/Adam Dinwoodie/noarch/release/git-filter-repo/git-filter-repo-2.38.0-1-src.hint
>>> ERROR: error while reading uploaded arch noarch packages from maintainer Adam Dinwoodie
>>> SUMMARY: 5 ERROR(s)
>>> ```
>>
>> Sigh.  Yeah, this isn't working well and is causing people problems, so
>> I've changed this validation failure from an error to a warning, for the
>> moment.
>>
>> I might remove it totally, or revise how it works in the future.
> 
> I definitely appreciate the principle of declaring this sort of thing!
> The current mechanism might not be working, but I suspect that's
> mostly an issue of deciding what we're trying to achieve with it, and
> what options there are for achieving that…
I think I misspoke here in saying "I".  Since there seems to be lots of 
people with opinions on this topic, if someone else wants to take the 
initiative and define how this is going to work, that would be great :) 
(Not least because I am limited in how much time I can devote to this 
currently)