Merged repo for protocol headers? Why are they split?

[Dylan Baker]

Quoting Daniel Martin (2017-11-21 01:59:42)
> Hi,
> 
> I've ever wondered why are the proto headers split up into distinct
> repos? (It takes "ages" to just copy (install) a few files with
> autotools.)
> 
> Dylan started to add meson support, but doing this for all protos
> sounds like a lot of copy'n'paste to do, lots of patches . Wouldn't it
> make more sense in general to merge all proto repos into one (meson
> only) and have options if you don't want a specific proto to be
> installed as we do with xcb?
> 
> Cheers,
>     Daniel
> 
> PS: A quick search revealed that a merge is possible even with keeping
> the history.

For reference here's the proto packages that archlinux provides:
bigreqsproto
compositeproto
damageproto
dmxproto
dri2proto
dri3proto
fixesproto
fontsproto
glproto
inputproto
kbproto
libxdmcp
presentproto
printproto
randrproto
recordproto
renderproto
resourceproto
scrnsaverproto
videoproto
xcmiscproto
xextproto
xf86dgaproto
xf86driproto
xf86vidmodeproto
xineramaproto
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: signature
URL: <https://lists.x.org/archives/xorg-devel/attachments/20171121/cac7e562/attachment.sig>