Hi, On 09/17/16 10:51, Jonas Smedegaard wrote: > Quoting Paul Gevers (2016-09-16 20:01:27) >> How are other JavaScript chains handling the lack of automatic API >> tracking? > > At least 16 packages unacceptably violates Debian Policy, according to > https://anonscm.debian.org/viewvc/secure-testing/data/embedded-code-copies?view=co
This was not what I meant. What I meant is how JavaScript is handling the lack of shlibs/symbols processing as we do during package building for libraries and depending packages. I would love to know how I can learn what version of $javascript-package I actually need for my package to work properly. >> Are there tools in the team to check for breakage? One of the stupid >> but powerful things that I do for the cacti package (a web-app) is to >> just recursively crawl all web-pages, I guess it must be possible to >> also check JavaScript execution. > > In theory we have several tools to emulate javascript-enabled browsing, Could you please hint which ones you have in mind? > I guess locally - *not* using Debian infrastructure - one might use npm Why not using Debian infrastructure, because one needs to download stuff that isn't in the package? I was thinking of running these tests as autopkgtest? Paul
signature.asc
Description: OpenPGP digital signature
-- Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
