[arch-dev-public] libx11/xorgproto dependency

[Jan Alexander Steffens]

On Sat, Dec 21, 2019 at 12:42 PM David Runge <dave at sleepmap.de> wrote:

> I'd go for b) as to me it seems the more correct approach (and doesn't
> require introducing further packages). Additionally, it is reflected in
> the package guidelines [1].
>

Unfortunately I think the guideline isn't very clear on what it means. It
is thus:

Build system of program A wants libraries B and C.
Library B depends on C.
You should add both B and C to A's depends.

But if the build system of program A wants only library B, you should not
add C to A's depends.

We now have many packages that want libx11 but say nothing about *proto,
yet they now need xorgproto as a makedepend.
Even worse, this extends further downstream, and packages building against
GTK now also need a makedepend on xorgproto.
I made a rough estimation and end up at ~3500 packages that are now broken.

Grepping for 'Requires:.*\wproto' through my local pkg-config files, these
packages directly reference a *proto and should have a dep on xorgproto:

libice
libx11
libxau
libxaw
libxcomposite
libxcursor
libxdamage
libxdmcp
libxext
libxfixes
libxfont2
libxft
libxi
libxinerama
libxkbfile
libxmu
libxrandr
libxrender
libxres
libxss
libxt
libxtst
libxv
libxxf86vm