A strict reading of policy now indicates that Build-Depends-Indep need not ever be satisfied when the clean target is called. Apparently this change was made to document autobuilder behavior when building packages that mix arch all and arch any components, but as I read it, the effect is broader. If build-depends-indep need not be satified any time the clean target is run, then I can imagine that some tool might be written to rely on that, and only install the build-depends before building a package that is only arch: all. Therefore it seemed to me that I should change the dozen or so arch all pacages I maintain to put debhelper in the build-depends (and generally everything in the build-depends for most of them since the split is useless unless the package builds both arch all and any and has a properly structured debian/rules -- only one of my packages bothers with that). When I did, linda complained: W: liblingua-en-words2nums-perl; Package has Build-Depends, but builds no arch-dependant packages. Is linda behind the times, or am I trying to follow policy too closely? Is this build-depends-indep split really of any value, or is it just complicating our lives for no good reason? -- see shy jo
Attachment:
pgprBY1V6fT2b.pgp
Description: PGP signature