[arch-dev-public] libx11/xorgproto dependency

Antonio Rojas arojas at archlinux.org
Sat Dec 21 09:12:17 UTC 2019

El 21/12/19 a las 9:41 Andreas Radke via arch-dev-public escribió:
> After some discussion on IRC these solution are possible:
> a) revert to make libx11 depend again on xorgproto headers. This is the
> pragmatic way and would not need any further work. It just installs
> header files to the user system that aren't needed in any way there. So
> we did in the past and I don't really like it as it's not correct to me.
> b) stay with changed libx11 and add xorgproto to packages that check
> for any of its headers. This needs to be done to an amount of ~300
> packages when hitting build errors over the next time.
> c) go an unusual way here and split libx11 into libx11, libx11-devel
> depending on xorgproto and maybe even libx11-xcb. This is the way
> distros go that support splitting libraries. It's probably the
> technical correct solution but will also require packages to
> makedepend on libx11-devel and save us no work.

I'm fine with either (a) or (b), both can be seen as correct for some definition of "dependencies". But please not (c), it doesn't really fix anything and it's an unnecessary divergence from our usual practice of not having split devel packages.

More information about the arch-dev-public mailing list