Hi Ghislain, On Tue, Dec 06, 2016 at 08:00:50AM +0000, Ghislain Vaillant wrote: > > > > 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.
I've uploaded with Architecture: any. > 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. Hmmm, this message droped in my inbox after uploading. I'm not sure how important this might be - in any case the package has built nicely. Could you please be more verbose what effect the additional dependency might have? Kind regards Andreas. -- http://fam-tille.de