On Tue, 2016-12-06 at 11:01 +0100, Andreas Tille wrote: > Hi Ghislain, > > 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.
Both libblas-dev and libblas-dev | libblas.so would lead to successful builds on autobuilders. The latter always pick libblas-dev in case an alternative implementation is not already installed. > Could you please be more verbose what effect the additional dependency > might have? It is only a big deal for local builds, where you might have a BLAS compatible package already installed (which provides libblas.so). Ghis