On 12/21/19 3:41 AM, Andreas Radke via arch-dev-public wrote:
> With this move I've "fixed" libx11 no more depending at runtime on
> xorgproto package. I think no headers belong to an end user system and
> the libx11 library itself doesn't depend on it. But we also ship
> libx11-devel part inside
Am Sat, 21 Dec 2019 19:47:39 +0200
schrieb Evangelos Foutras via arch-dev-public
:
> @Andreas: Can you go ahead and add xorgproto back to libx11? Better to
> have 1.5 MiB of headers installed than add seemingly unrelated
> xorgproto build dep to packages failing to build or have features
>
On December 21, 2019 9:41:46 AM GMT+01:00, Andreas Radke via arch-dev-public
wrote:
>With this move I've "fixed" libx11 no more depending at runtime on
>xorgproto package. I think no headers belong to an end user system and
>the libx11 library itself doesn't depend on it. But we also ship
On Sat, 21 Dec 2019 at 18:13, Jan Alexander Steffens via
arch-dev-public wrote:
>
> 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
On Sat, Dec 21, 2019 at 12:42 PM David Runge 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
On Sat, Dec 21, 2019 at 12:18 PM Allan McRae via arch-dev-public <
arch-dev-public@archlinux.org> wrote:
> On 21/12/19 7:31 pm, Evangelos Foutras via arch-dev-public wrote:
> > Downstream consumers of libx11 shouldn't have to know and account for
> > libx11's headers/pkg-config files referencing
First of all, thanks for doing the cleanup! :)
On 2019-12-21 09:41:46 (+0100), Andreas Radke via arch-dev-public wrote:
> Please vote.
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
On 21/12/19 7:31 pm, Evangelos Foutras via arch-dev-public wrote:
> Downstream consumers of libx11 shouldn't have to know and account for
> libx11's headers/pkg-config files referencing xorgproto. A
> libx11-devel package would depend on xorgproto. Since there's no
> separate -devel package, the
Downstream consumers of libx11 shouldn't have to know and account for
libx11's headers/pkg-config files referencing xorgproto. A
libx11-devel package would depend on xorgproto. Since there's no
separate -devel package, the dependency stays with the regular libx11
package.
You already called (a)
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
With this move I've "fixed" libx11 no more depending at runtime on
xorgproto package. I think no headers belong to an end user system and
the libx11 library itself doesn't depend on it. But we also ship
libx11-devel part inside the package and this indead depends on
xorgproto headers. The libx11
11 matches
Mail list logo
