Re: xorgproto replacing lots of fooproto

[Thomas Klausner <tk%giga.or.at@localhost>]

I've now switched all packages to use xorgproto.

I've tested this with modular x.org and ~500 affected packages, which
still built as well as before for me (some better, because I fixed
them ;) ).

I did not provide a builtin.mk file because I couldn't think of a
reasonable solution, and the xorgproto package is small and
built-dependency only.

pkgtools/x11-links might need fixes, I hope someone can do that for
native builds.

Thanks,
 Thomas

On Sun, Feb 11, 2018 at 09:15:02PM +0100, Thomas Klausner wrote:
> I've just imported an 'xorgproto' package for this.
> 
> It includes the headers that are currently spread over dozens of other
> packages.
> 
> I suggest just replacing the corresponding bl3.mk inclusions with one
> for this package and removing the old proto packages.
> 
> I'm not sure how to handle builtin.mk (didn't create one yet). Should
> it just check for one of the pc files and assume the others are there,
> or does anyone have a better idea?
> 
>  Thomas
> 
> ----- Forwarded message from Adam Jackson <ajax%nwnk.net@localhost> -----
> 
> Date: Mon, 05 Feb 2018 14:30:07 -0500
> From: Adam Jackson <ajax%nwnk.net@localhost>
> To: "xorg-announce%lists.x.org@localhost" <xorg-announce%lists.x.org@localhost>
> Cc: xorg%lists.x.org@localhost
> Subject: [ANNOUNCE] xorgproto 2018.1
> 
> This package combines the protocol headers, which were formerly
> scattered in individual packages. At this point none of them are
> changing rapidly enough to justify such fine granularity, particularly
> when what changes do occur tend to affect multiple extensions at once
> (Present and DRI3 for example). The individual protocols are still
> installed as separate pkg-config modules, and consumers should continue
> to use the per-protocol package version numbers.
> 
> This release includes both an autotools-based and a meson-based build
> system. The meson build is slightly faster and more convenient for CI
> and embedding, and it is expected to become the default at some point.
> However the autotools build is "official" at the moment, in the sense
> that it was used to build the release and is generally expected to
> work. Please report any issues you have with either one.
> 
> <X11/Xfuncproto.h> is no longer dynamically generated according to the
> host platform. As a result, this release no longer makes any attempt to
> be compatible with pre-C89 compilation environments, which hopefully
> nobody would ever notice.
> 
> git tag: xorgproto-2018.1
> 
> https://xorg.freedesktop.org/archive/individual/proto/xorgproto-2018.1.tar.bz2
> MD5:  c110fe52f9cf7d92f4f2cd6a04840676  xorgproto-2018.1.tar.bz2
> SHA1: c40c6858928dfaaf9fd7128c7927113668c85864  xorgproto-2018.1.tar.bz2
> SHA256: 7eb9ea8a204499d2d7a5958db82e57a56a63eb4ff12c19ebf3bd6b82d6ac1799  xorgproto-2018.1.tar.bz2
> SHA512: eaad8947f8cda4683bd952706feaa926eed06c508925d3bed7c9a610f925844d3546bbfe49b5403220ca812d63442ca6a72e65ecc50a71899aadf60875156800  xorgproto-2018.1.tar.bz2
> PGP:  https://xorg.freedesktop.org/archive/individual/proto/xorgproto-2018.1.tar.bz2.sig
> 
> https://xorg.freedesktop.org/archive/individual/proto/xorgproto-2018.1.tar.gz
> MD5:  3af8cb82af512050c0000badbd67a948  xorgproto-2018.1.tar.gz
> SHA1: efa8516bbb939eca3a2abdeee4c9a9ccffc1e059  xorgproto-2018.1.tar.gz
> SHA256: a386126eee0cd91ccb09117144b5b207e9d067983abfd38210ae91e377c32c49  xorgproto-2018.1.tar.gz
> SHA512: f9f42f0973d8f81bf7cc5f0ecef5a2aac2bd81aa182ec601a27cb46bbe5c2ec466fcd53933695d64fb0d9ce710a402ee81744392704843ddaec5f00fbf717599  xorgproto-2018.1.tar.gz
> PGP:  https://xorg.freedesktop.org/archive/individual/proto/xorgproto-2018.1.tar.gz.sig
> 
> - ajax
> _______________________________________________
> xorg-announce mailing list
> xorg-announce%lists.x.org@localhost
> https://lists.x.org/mailman/listinfo/xorg-announce
> 
> ----- End forwarded message -----
>