Le 21/03/2020 à 18:36, Jonas Smedegaard a écrit : > Quoting Xavier (2020-03-21 18:22:37) >> currently we use Build-Depends to push all our dependencies. This >> makes Multi-Arch reports a lot of problems while most of our packages >> are scripts only. >> >> As other languages, I think we should use Build-Depends-Indep for all >> Javascript dependencies. Example: >> >> Build-Depends: debhelper-compat (= 12) >> Build-Depends-Indep: pkg-js-tools (>= 0.9.20~) >> , node-tap <!nocheck> >> , ... >> >> But perhaps am I wrong here ? >> Experimented DD advises are welcome ;-) > > (I think you mean _experienced_ in last sentence above ;-) ) > > As I understand it, B-D-Indep should be used _only_ when a source > package builds _both_ architecture-dependent and > architecture-independent binary packages, and is then used to indicate > which build-deoendencies can be skipped when only building the > arch-independent parts. > > In other words, not "for all Javascript dependencies" (if I understand > it correctly). > > > - Jonas
OK, but we have many (not all) packages that have a "node-foo could be marked Multi-Arch: foreign" even if they are installed in /usr/share/nodejs and Perl packages don't have such "action needed" in tracker.d.o Looking at Perl practices, it seems that "architecture: all" packages uses only Build-Depends-Indep except for debhelper-compat So is this a way to improve multi-arch ? -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel