Hi,
In several packages I maintain there are programs that function like
pkg-config
(adios-config in adios; dap-config in libdap-dev). These then contain
architecture-specific
information similar to pkg-config files.
What is the preferred solution for handling these in the multi-arch
debian world?
Currently I am working on providing pkg-config .pc files as a replacement
(and requesting that upstream deprecate the *-config scripts); I could
rewrite the adios_config
and dap-config scripts to read the pkg-config file information, but I'm
unsure how
pkg-config works in multiarch when multiple arch versions of a library
are installed;
how is pkg-config expected to behave when multiple architecture versions
of a lib
are installed, and if I make, e.g. adios_config return the same results,
should I ship
adios_config in /usr/bin of libadios-dev in a multiarch version?
Regards
Alastair
--
Alastair McKinstry ,<alast...@sceal.ie> ,<mckins...@debian.org>
http://blog.sceal.ie
Anyone who believes exponential growth can go on forever in a finite world is
either a madman or an economist - Kenneth Boulter, Economist.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e710074.8060...@debian.org
