On Thu, May 10, 2018 at 10:56 PM, Chris Lamb <la...@debian.org> 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 >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 > case of missing dependencies, just as one example.. missing dependencies could be detected but worst is conflicts. It is regression prone. > >> - for every optionnal depends on package.json check debian control >> suggest or recommand > > Did you mean "*in* package.json" (not "on package.json")? If so, I was > not aware package.json have optional dependencies. Yes, in package.json, they are optional (seldom used) depends > > (Isn't this stuff autogenerated from the package.json by somen? Then > there could not be a conflict...) No it is manually done... I know crap over crap. Lintian is good for cleaning, so use lintian > > Anyway, I'm sorry can't seem to prase what you are saying and there is > quite a bit of ambiguity. No problem. I am on irc in case of problem Bastien > > > Best wishes, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk > `-