Dear Bastien,
> >> - for every depends in package.json check debian control depends
> > ^^^
> > Do you mean in the "devDependencies" key?
>
> no the Dependencies key, the devDependencies should be checked against
> source package depends
Getcha, I think. (to clarify, all devDep
On Thu, May 10, 2018 at 10:56 PM, Chris Lamb wrote:
> Hi Bastien,
>
>> - for every depends in package.json check debian control depends
> ^^^
> Do you mean in the "devDependencies" key?
no the Dependencies key, the devDependencies should be checked against
source package depends
Hi Bastien,
> - for every depends in package.json check debian control depends
^^^
Do you mean in the "devDependencies" key? Clarification on exactly
what "check" means here would be needed here too; whilst your bug
title says "detect conflict", that doesn't strictly include the
On Wed, May 9, 2018 at 8:34 PM, Chris Lamb wrote:
> Hi Bastien,
>
>> If package is section javascript search all file named package.json, parse it
>> and control against control depends (including optional that go to recommand
> ^^^
Hi Bastien,
> If package is section javascript search all file named package.json, parse it
> and control against control depends (including optional that go to recommand
> or suggest).
^^
I can't parse thi
Package: lintian
Version: 2.5.84
Severity: minor
Hi,
Npm package use package.json for checking version
(see https://docs.npmjs.com/getting-started/semantic-versioning).
control use the debian way.
it will be nice to detect difference between the package.json file and the
control file
If pac
6 matches
Mail list logo
