Force dpkg-buildpackage to specify exact dependencies for some packages?
1
vote
1
answer
99
views
I'm building an app that depends on Qt6 and by default
dpkg-buildpackage
generates a >=
dependencies for shlibs dependencies I didn't explicitly specify . So specifying:
Depends: ${shlibs:Depends}
Causes:
$ dpkg-query --show -f '${Depends}' mypackage
... qt6-base (>= 6.7.2), ...
The problem is that Qt requires the exact specific version that the app was built against in order to run. If the system has qt6-base
version 6.8.0
installed, my app will install but will fail to run - how can I prevent that?
I don't want apt
to update my app until I have a version that explicitly supports the exact version of Qt that is available on the system (and/or prevent updating Qt until I have released an appropriate version).
I know I can add manual explicit dependencies for each and every Qt package I depend on - and then update the version manually every time I build with a new Qt version - but this is going to be so much trouble. I would expect there would by an option of something like "for packages that have the text 'qt' in their name, use a =
dependency instead of a >=
".
Asked by Guss
(13256 rep)
Oct 29, 2024, 10:19 AM
Last activity: Oct 29, 2024, 11:08 AM
Last activity: Oct 29, 2024, 11:08 AM