Before the sbuild integration, additional NPM install / build dependencies could be added to NPM_EXTRA_DEPS. With sbuild support, these now have to be listed twice: in the NPM_EXTRA_DEPS and in DEBIAN_BUILD_DEPENDS. The reason is, that the sbuilder uses the dependencies listed in debian/control, while the do_install_npm task uses NPM_EXTRA_DEPS.
Also, the format of both variables has to be different (space separated vs. debian depends format).
I don't know if this is intentional, or if we should add logic that creates a comma separated list of NPM_EXTRA_DEPS and adds it to DEBIAN_BUILD_DEPENDS.
Before the sbuild integration, additional NPM install / build dependencies could be added to
NPM_EXTRA_DEPS
. With sbuild support, these now have to be listed twice: in theNPM_EXTRA_DEPS
and inDEBIAN_BUILD_DEPENDS
. The reason is, that the sbuilder uses the dependencies listed indebian/control
, while thedo_install_npm
task usesNPM_EXTRA_DEPS
. Also, the format of both variables has to be different (space separated vs. debian depends format).I don't know if this is intentional, or if we should add logic that creates a comma separated list of
NPM_EXTRA_DEPS
and adds it toDEBIAN_BUILD_DEPENDS
.Real-world example: