svn commit: r421549 - in head: . Mk

[Kubilay Kocak]

On 9/09/2016 7:06 AM, Mathieu Arnold wrote:
> Le 08/09/2016 à 16:03, Kubilay Kocak a écrit :
>> What if a piece of software doesn't have 'cleanly' (what is the
>> actual definition we should use?)
> 
> If you don't know, you just don't decide your self, you live it
> absent, or ask upstream.
> 

I agree, but this is precisely what I think will *not* happen with NONE
as the name, and the exact reason for my original reply.

UNDEFINED is less ambiguous and means 'we looked but we can't tell, so
don't do anything (package, distribute) that may be illegal), which
appears to be the intent of the behaviour/implementation that was committed.

UNDEFINED is just a step more explicit than empty(LICENSE), which is
something else we want. Someone has looked, its unclear, undefined, not
documented, not explicit, <some-other-standard>, so set it (explicitly)
as such.

Then give maintainers/developers a 6 month heads-up on empty(LICENSE)
becoming 'does not package/distribute source' as well, and watch ports
upgrade to their actual LICENSE=, or LICENSE=UNDEFINED.