[Dune] state of Debian packages for dune

[Markus Blatt]

Hey Ansgar,

On Sun, Mar 18, 2012 at 02:50:37PM +0100, Ansgar Burchardt wrote:
> Ansgar Burchardt <ansgar.burchardt at iwr.uni-heidelberg.de> writes:
> > The packages for dune-{common,istl,localfunctions} should be ready.  The
> > other modules still have some minor things I would like to fix before
> > uploading them (see below).
> 
> dune-common[1] and -istl[2] are now uploaded to experimental.
> 

thanks for the work. I just tried them to see what the problem with
flyspary 1100 is.

The problem is that I assumed that dune.module and dune-common.pc both
get installed to ${libdir}//dunecontrol/dune-common and
/pkg-config/dune-common, respectively. This is the case when using
make install. In contrast to this in the Debian packages dune-common.pc
resides in ${libdir}/pkgconfig and dune.module in
${libdir}/../dunecontrol/dune-common, where libdir is
/usr/lib/x86_64-linux-gnu according to "pkg-config  --variable=libdir
dune-common". 

Is this intented and common Debian policy? If so, is there a
convenient way to mimik this in automake?

Cheers,

Markus

-- 
Do you need more support with DUNE or HPC in general? 

Dr. Markus Blatt - HPC-Simulation-Software & Services http://www.dr-blatt.de
Hans-Bunte-Str. 8-10, 69123 Heidelberg, Germany
Tel.: +49 (0) 160 97590858  Fax: +49 (0)322 1108991658