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

2020-12-23 Thread Dominique Dumont
On Thu, 2 Nov 2017 14:28:12 +0530 Pirate Praveen wrote: > Most ruby gems have the license information in .gemspec file .gemspec files are written in Ruby. I don't really know how to extract the relevant information from this file. I don't think using regexp to parse the gemspec file would be

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

2020-12-21 Thread Dominique Dumont
On Monday, 21 December 2020 12:05:20 CET you wrote: > I guess it should be the other way around? oh my I can't believe I did not see this bug ... ok, I'm going to fix this.

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

2020-12-21 Thread Andrej Shadura
On 20/12/2020 19:12, Dominique Dumont wrote: > On samedi 12 décembre 2020 19:32:54 CET you wrote: >> Have you had a chance to have a look at it? > > Done. The last version of libconfig-model-dpkg-perl can parse Config.toml > file. > > Please check if this fits your requirements. Checking the

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

2020-12-20 Thread Dominique Dumont
On samedi 12 décembre 2020 19:32:54 CET you wrote: > Have you had a chance to have a look at it? Done. The last version of libconfig-model-dpkg-perl can parse Config.toml file. Please check if this fits your requirements. All the best Dod

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

2020-12-15 Thread Andrej Shadura
On 13/12/2020 15:43, Dominique Dumont wrote: > Hi > > Sorry for the delay. > > On Sat, 12 Dec 2020 19:38:14 +0100 Andrej Shadura > wrote: >>> Have you had a chance to have a look at it? :) > > That's a good start. At least, this patch tells me how to retrieve the > relevant information from

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

2020-12-13 Thread Dominique Dumont
Hi Sorry for the delay. On Sat, 12 Dec 2020 19:38:14 +0100 Andrej Shadura wrote: > > Have you had a chance to have a look at it? :) That's a good start. At least, this patch tells me how to retrieve the relevant information from the toml file. However, your patch implies that the

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

2020-12-12 Thread Andrej Shadura
On 12/12/2020 19:32, Andrej Shadura wrote: > Have you had a chance to have a look at it? :) For your convenience, I’ve rebased it to the current HEAD. -- Cheers, Andrej >From 393f06dcf7be43488b3410a38308bf12df321707 Mon Sep 17 00:00:00 2001 From: Andrej Shadura Date: Fri, 13 Dec 2019

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

2020-12-12 Thread Andrej Shadura
Hi, On Fri, 13 Dec 2019 16:11:23 +0100 Andrej Shadura wrote: > 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. Almost exactly a

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

2019-12-13 Thread Andrej Shadura
Hi, On Sun, 05 Nov 2017 11:49:29 +0100 Dominique Dumont 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

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

2017-11-06 Thread Dominique Dumont
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

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

2017-11-02 Thread Pirate Praveen
package: libconfig-model-dpkg-perl version: 2.102 severity: wishlist 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