On Mon, Jun 27, 2011 at 05:01:15PM +0200, Sven Joachim wrote:
> I see two possible solutions:
>
> 1) Mark ncurses-bin Multi-Arch: foreign.
> 2) Move ncurses{w,5}-config to their respective -dev packages and drop
> the ncurses-bin dependency.
>
> 1) has the disadvantage that the output of "ncurses5-config --libs" and
> "ncurses5-config --libdir" is incorrect for foreign arches. The
> downside of 2) is that it becomes impossible to make the -dev packages
> Multi-Arch: Same (AIUI this is currently not allowed anyway, but may be
> in the future[2]).
It certainly is allowed (and becoming commonplace) now. And I see that
you've since marked ncurses-bin Multi-Arch: foreign, which seems
reasonable.
We could just declare that anyone who wants correct ncurses
configuration in a multiarch universe needs to use pkg-config instead.
This already has broadly sensible cross-building support, whereas
attempting that with ncurses{5,w5}-config would require work more or
less equivalent to just switching to pkg-config.
I don't know whether you know this, but there definitely exist packages
that require both the build and host architecture versions of
libncurses{5,w5}-dev in order to cross-build successfully, due to
performing both native and cross passes when cross-building. texinfo is
such a case which I ran across recently. Therefore, I don't think a
solution that prevents the -dev packages becoming Multi-Arch: same is
correct.
Cheers,
--
Colin Watson [[email protected]]
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
