[Dune] state of Debian packages for dune

[Ansgar Burchardt]

Hi,

On 05/22/2012 03:03 PM, Markus Blatt wrote:
> 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?

Installing libraries to an architecture-qualified path is done in Debian
to allow installing the package for multiple architectures on the same
time (say i386 and amd64).  It's a fairly recent thing.

dunecontrol in Debian has a small patch to look in the right
subdirectory, but as the name of that directory varies between
architectures I haven't forwarded it yet.  In any case the fix you
committed (r6746) only works on amd64.

Regards,
Ansgar