[opam-devel] licensing handling for Opam

[Florent Monnier]

2013/4/4, Anil Madhavapeddy <anil at recoi...>:
> On 4 Apr 2013, at 08:13, Florent Monnier <monnier.florent at gmai...> wrote:
>> 2013/04/04, Anil Madhavapeddy <anil at recoi...>:
>> [...]
>>> OASIS has a nice library to handle all this doesn't it?  CCing Sylvain
>>> to see if it can be separately used by OPAM.
>>
>> Be carefull though, such a solution can be for sure a help,
>> but a human check is still necessary.
>>
>> This is very rare but sometimes there is a mismatch between the
>> licensing information provided in the _oasis file and in the headers
>> of the source code.
>> There is currently at least one lib like this.
>
> You should report these upstream to get them fixed.  OPAM isn't really the
> place to hold local patches (as this metadata could be used by other package
> managers too).

Yes I know.
It was just a warning against expecting to get things done
automatically without human checking the results.

(if I haven't reported upstream it's because I've seen it at a moment
when I couldn't report immediatly and the days after I didn't remember
which lib it was)

-- 
Cheers