Bug#973702: licensecheck should read "license" field from package.json files
Xavier
yadd at debian.org
Tue Nov 3 19:28:02 GMT 2020
Le 3 novembre 2020 19:50:52 GMT+01:00, Jonas Smedegaard <jonas at jones.dk> a écrit :
>Quoting Xavier (2020-11-03 18:35:48)
>> Le 03/11/2020 à 18:30, Jonas Smedegaard a écrit :
>> > Quoting Jonas Smedegaard (2020-11-03 17:19:10)
>> >> Quoting Xavier Guimard (2020-11-03 17:07:02)
>> >>> when launching licensecheck in a nodejs module, I'd like to see
>> >>> licensecheck reveals which license is used in package.json
>> >>
>> >> Licensecheck currently operates on files.
>> >>
>> >> package.json contains a field to state license for a _project_ which
>> >> is something different.
>> >>
>> >> How would you expect licensecheck would handle that?
>> >
>> > Maybe the above came across as needlessly agressive.
>> >
>> > Thanks for reporting this. Reporting it is appreciated on its own -
>> > you need not "defend" this issue.
>> >
>> > I agree that it would be nice if licensecheck could recognize
>> > copyright and licensing information in all the many forms they are
>> > hinted - including project-wide hints.
>> >
>> > What I meant to ask is if you have some ideas how licensecheck could
>> > sensibly report such non-file-specific hints?
>>
>> Hi,
>>
>> thanks for taking care of this and licensecheck! I never take a look
>> at how licensecheck works, so no idea for now, but I'll try to
>> understand licensecheck, then search how we could do this
>
>I don't mean how to codify.
>
>I just mean what could the output from licensecheck look like.
>
>
> - Jonas
For me, we can just say that this file is covered by license. This is the same case as "License" file (whole project), isn't it?
--
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma brièveté.
More information about the pkg-perl-maintainers
mailing list