On 2012-12-07 01:30 +0100, Colin Watson wrote:
> 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.
Right, since I initially also marked the -dev packages Multi-Arch: same,
which turned out to be premature since the headers unfortunately are
arch-dependent.
> 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.
Actually, the only thing in ncurses{w,}5-config which differs across
architectures is the "--libdir" option, and I don't think this causes
real problems in cross-building. The "--libs" option I also mentioned
is already taken care of by the 03-debian-ncursesconfig-omit-L.diff
patch.
> 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.
Thanks, I was not aware of that.
> Therefore, I don't think a solution that prevents the -dev packages
> becoming Multi-Arch: same is correct.
Making the -dev packages coinstallable is definitely a goal for Jessie,
please followup on #689131 if you're interested. The current bug should
just be closed, I think.
Cheers,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
