Re: wlroots backport?
Demi Marie Obenour <[email protected]>
| Newsgroups | gmane.linux.debian.backports.general |
|---|---|
| Message-ID | <ZNuh8G/a1Pjn3J5n@itl-email> |
On Mon, Aug 14, 2023 at 08:47:31PM +0300, Michael Tokarev wrote: > 14.08.2023 02:28, Demi Marie Obenour wrote: > > Is there any interest in backporting the latest version of wlroots > > (0.16.2) to bookworm? wlroots upstream only supports the latest version > > and the wlroots API is unstable, so compositors that rely on 0.16.x will > > not work with the version in stable (0.15.x). > > There's an issue with wlroots and backporting: it is the soname of libwlroots > library. We don't gain much by backporting just the wlroots, the users of > the library has to be rebuild or backported too. I have written a Wayland compositor for Qubes OS that relies on wlroots. That said, I’m wondering if I should just link wlroots statically, as my compositor will follow upstream wlroots releases. -- Sincerely, Demi Marie Obenour (she/her/hers) Invisible Things Lab
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmTbofAACgkQsoi1X/+c IsG7DRAAuESwVsI9/5noDJA7+DaqxgGgREK0ezexvEA2lmgzN4yBTUTa9+y0CWst eGuLTL5jIX3pqpRVgX5mCkwcp6vsWJW9YTk39vZLt3UfEyjMRyogpESet9+v/HWe /5yXBaheP6FzvfPNGskyW2QRXYLEmUA4f3H3w6eLCAZj6YIjquEG8Mtm9xkgBEHZ 2AXC15aXj0v0+9RYyLVsWr20wtZGLK2qdmKdmzqBn9z8EkRtX/+4W9ajXM4O3QDS JW/LNSiv7SGF9N/ztGYzCkWjoRoYnhkC2+sYpJiyOaV/yp5nIRiT6VIdID1yuD4V E5cwX+mDNv65eC2ElPQwRxkAn37rmjge3EH8w62xHC8oR8dLtIBOwuQa9B5k44Yw n9RwRAg8bvTXKZgHjULQMJ6pDdHim/e4cfL1jzDDWpNmvS2zS7UeAB0h2uxl1oVi JdEeSJ76JtHsd436wrGQvOXECtaD8dX9Rf8bN93X2IjWelgKoUaOL15kcfMCixJ1 WqjxV2K+S5lbwC7Two9d9zvmUH63ZiiQfP65Xvo2YvzIGAbY6ufDOc2CcQV3Kzx4 KW1H0OFVO7KpOnimotPQeKMvG4IFi1nVJW5pE1eXnHNOlf0AF1dqnW8i3KZzftn7 FvdVKEYQKC/VgApjv9CLKjl5ESzaj/sOSvjPaHjI582tcmhSSwg= =Ymhp -----END PGP SIGNATURE-----