Bug#880556: parse upstream metadata files like package.json or .gemspec files

[Andrej Shadura]

Hi,

On Sun, 05 Nov 2017 11:49:29 +0100 Dominique Dumont <dod at debian.org> wrote:
> On Thursday, 2 November 2017 14:28:12 CET you wrote:
> > Most ruby gems have the license information in .gemspec file and
> > similarly most nodejs modules have this information in package.json file
> > (likely for similar files for other languages). It would be good to
> > parse it and use that information.
> 
> Yes, good idea. I'm thinking also to parse the content of META.yml to retrieve 
> the same kind of information.
> 
> Do you have examples of one ruby and one nodejs package that could be used as 
> a reference ?
> 
> Then I just need to find time to do this...

Please find attached proof of concept scanner for Rust Cargo.toml files.
I’m not fluent in Perl, and I wasn’t sure where exactly to put this
piece of code, but this is something you probably can polish up a bit.

Thanks for considering this.

-- 
Cheers,
  Andrej
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-WIP-Scan-Rust-source-code-getting-the-defaults-from-.patch
Type: text/x-patch
Size: 1744 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-perl-maintainers/attachments/20191213/82551f46/attachment-0001.bin>