On Tue, 2016-12-06 at 08:11 +0100, Andreas Tille wrote: > Hi Gregory, > > On Mon, Dec 05, 2016 at 06:52:07PM -0500, Gregory Sharp wrote: > > > > > I admit if there was an explicit reason I simply forgot it (but its also > > > for amd64, right). > > > > The architectures are amd64 and i386 because libinsighttoolkit4-dev > > is only available on those platforms. If there is a more elegant > > way to represent this constraint I would be happy to remove. > > The more elegant way is to simply specify "any". Autobuilders will > notice themselves whether a Build-Dependency exists or not and simply do > nothing if a Build-Dependency is missing.
I second this. I have a similar source package (asl) depending on VTK, which is also not available on all architectures. It is marked any nonetheless and has been built by the builders wherever all dependencies were satisfiable. Other comments: - "Add libblas-dev dependency (sub-dependency of libdlib-dev) to plastimatch" If libdlib-dev is missing a dependency (BLAS), it should be fixed there. Transitive dependencies should not happen unless the dependency in question is optional (like a specific backend, or extra feature). If plastimatch directly depends on BLAS, then the right dependency should be libblas-dev | libblas.so, to allow any implementation of BLAS (netlib, atlas or openblas) to fulfill it. Cheers, Ghis
