fdd6dadb4a
The packages we should build are restricted by: * Package configuration in debian/config (limits which binary packages are included in debian/control) * Architecture (specified per package in debian/templates/control.* and then in debian/control) * Build profile (specified per package in debian/templates/control.* and then in debian/control) The logic for these restrictions is currently repeated in debian/rules.real, but sometimes it becomes inconsistent with debian/control (as with my recent changes for libbpf). dh_listpackages reads debian/control and filters it by the current host architecture and build profiles, so that it reliably reports which packages we should build. Therefore: * Replace the logic in debian/rules.real with checks for package names in the output of dh_listpackages * Remove the redundant flag variables passed by debian/rules and debian/rules.gen * Remove the special-casing of stage1 in debian/rules and debian/rules.gen |
||
---|---|---|
debian |