you may have already done this analysis, Alberto, but fwiw what I see is that dpkg-architecture is used at runtime to get the multiarch path - however, this is always called in the context of the native architecture, so this can instead be calculated at build-time and embedded in the binary since this is in an arch-dependent package. That would solve the problem of needing dpkg-dev at runtime.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1880564 Title: ubuntu-drivers-common now pulls in build tools on end-user systems Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Focal: Triaged Bug description: In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of build-essential on upgrades (or just binutils and make and patch if you pass --no-install-recommends). This needs to be reverted and fixed differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
