Bug#894472: libqt5waylandclient5-dev: Missing QtWayland private headers
Hi! El jue., 30 jul. 2020 18:03, Nicholas Guriev escribió: > Telegram Desktop since 2.2.0 version requires these privates headers for > Wayland > integration. I had to copy a piece of build tree of the > qtwayland-opensource-src > package to telegram-desktop. Please install all the headers to ordinary > "-dev" > binary packages or provide a special "-private-dev" package. > > > https://salsa.debian.org/debian/telegram-desktop/-/commit/41e7ad4cdb6528a6659d61b68facb543958365be#a243a023b669d91df064d7708b91117d55c6f55d We avoid this as much as possible because it adds is lots of burden whenever we push a new Qt version in the archive. We only provide the private headers we need to be able to build Qt, but not more. Upstream should not be using private headers, they are private for a reason.
Bug#894472: libqt5waylandclient5-dev: Missing QtWayland private headers
Telegram Desktop since 2.2.0 version requires these privates headers for Wayland integration. I had to copy a piece of build tree of the qtwayland-opensource-src package to telegram-desktop. Please install all the headers to ordinary "-dev" binary packages or provide a special "-private-dev" package. https://salsa.debian.org/debian/telegram-desktop/-/commit/41e7ad4cdb6528a6659d61b68facb543958365be#a243a023b669d91df064d7708b91117d55c6f55d signature.asc Description: This is a digitally signed message part
Bug#894472: libqt5waylandclient5-dev: Missing QtWayland private headers
Control: tag -1 wontfix Hi Pier! El viernes, 30 de marzo de 2018 17:18:49 -03 Pier Luigi Fiorini escribió: > Package: libqt5waylandclient5-dev > Version: 5.10.1-2 > Severity: normal > > Dear Maintainer, > > Please include both QtWaylandClient and QtWaylandCompositor private headers > as they might be used by other software. > > Looks like they are removed on purpose: > > https://salsa.debian.org/qt-kde-team/qt/qtwayland/blob/master/debian/rules#L > 33 Yes, they are removed on purpose. > but people writing custom Wayland protocol implementations sometimes need > them not to mention client extensions that can only be implemented using > private headers. Then the best way forward is to work with upstream to make such API stable, public API. That needs to be done directly with upstream, not trough us. > Other Qt modules provide private headers in Debian, I don't see why > QtWayland doesn't. That's very simple: we only expose private API needed by other Qt submodules. Kinds regards, Lisandro. -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#894472: libqt5waylandclient5-dev: Missing QtWayland private headers
Package: libqt5waylandclient5-dev Version: 5.10.1-2 Severity: normal Dear Maintainer, Please include both QtWaylandClient and QtWaylandCompositor private headers as they might be used by other software. Looks like they are removed on purpose: https://salsa.debian.org/qt-kde-team/qt/qtwayland/blob/master/debian/rules#L33 but people writing custom Wayland protocol implementations sometimes need them not to mention client extensions that can only be implemented using private headers. Other Qt modules provide private headers in Debian, I don't see why QtWayland doesn't. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libqt5waylandclient5-dev depends on: ii libqt5waylandclient5 5.10.1-2 Versions of packages libqt5waylandclient5-dev recommends: ii qtwayland5-dev-tools 5.10.1-2 libqt5waylandclient5-dev suggests no packages. -- no debconf information
