Hi Helmut! On Wed, Jan 30, 2019 at 06:36:39AM +0100, Helmut Grohne wrote: > A number of qt-related projects manage their translations using > lrelease. The current packaging of qmake implies that lrelease only > works when you have a native qmake installed. When you only have a > foreign qmake (e.g. due to Build-Depends: qt5-qmake), lrelease prints an > error message and exists successfully. Arguably, this is a policy 4.6 > violation. Sometimes it is noted due to missing files at dh_install > time. Other times, one gets a broken build. > > In a discussion with Lisandro and Dmitry, we packages that use lrelease > are a minority. Therefore they should simply add qt5-qmake:native to > Build-Depends. This is a simple task once you know that it needs doing.
One thing bothers me: it is perfectly possible to use lrelease without qmake at all. All you need is have qttools5-dev-tools:native installed and call /usr/lib/qt5/bin/lrelease during build. You can do it from any non-qmake buildsystem, or even directly from debian/rules. I have a package that calls lrelease from Python’s setup.py (though this package is pure Python, so it is not affected in any case). Do you have a list of packages where adding qt5-qmake:native will actually make them cross-buildable? -- Dmitry Shachnev
signature.asc
Description: PGP signature
