Bug#909740: libsdl2-dev: No longer multi-arch co-installable

Hugh McMaster hugh.mcmaster at outlook.com
Sun Dec 8 13:03:04 GMT 2019


Hi Simon,

Thank you for revisiting this bug and implementing various solutions. I
know we'd scoped some of this out a while ago -- in theory, at least -- so
your work is most appreciated.


On Fri, 6 Dec 2019 at 10:21, Felix Geyer <fgeyer at debian.org> wrote:
>
> Hi Simon,
>
> On 27.11.19 20:18, Simon McVittie wrote:
> > In an attempt to unblock this bug I've implemented several versions of a
> > solution to it, so that the SDL2 maintainers can choose their favourite
> > and merge it.
> >
> > [...]
> >
> > Do the SDL2 maintainers have any comments on these MRs, or preference
> > between them?
>
> Thanks a lot for putting in all the work to implement, test and summarize
them!
>
> I'm leaning towards patching sdl2-config to call pkg-config
> (https://salsa.debian.org/sdl-team/libsdl2/merge_requests/5).
> My hope is that most software uses pkg-config or cmake to find SDL2.
> This solution wouldn't introduce any weirdness (forwarding header) into
> the default use cause.
>
> I'll merge that one unless someone wants to convince me otherwise soon ;)

After reviewing the four proposals, I too prefer the pkg-config solution to
the others. That said, your proposal using the Debian-specific header is
wonderfully simple.

In the longer term, I'm hoping there will be a push at some point to no
longer install sdl2-config, since that will simplify some of the issues
encountered here. Upstream have made it optional to install sdl2-config in
2.0.10.

Hugh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-sdl-maintainers/attachments/20191209/a01f5fdb/attachment.html>


More information about the Pkg-sdl-maintainers mailing list