Quoting Simon McVittie (2023-07-17 12:10:52) > On Mon, 17 Jul 2023 at 08:57:51 +0000, Holger Levsen wrote: > > On Sun, Jul 16, 2023 at 11:41:36AM +0100, Simon McVittie wrote: > > > On Sun, 16 Jul 2023 at 00:03:00 +0200, Adam Borowski wrote: > > > > due to Build-Depends > > > > being inadequate (per the Policy, B-D-Indep are _not_ necessarily > > > > installed) > > > > > > For completeness, B-D-Arch are not guaranteed to be installed during > > > clean either. > > > > I wonder what's the point of B-D-Arch And B-D-Indep then? > > The point is the same as it always was: primarily to exclude large > dependencies from a `dpkg-buildpackage -B` build chroot (like the official > buildd for each architecture) if they are only needed when building > Architecture: all packages such as documentation, and secondarily to > exclude large dependencies from a `dpkg-buildpackage -A` build chroot > (like the official "all" buildd) if they are only needed when building > Architecture: any packages.
additionally, moving build dependencies from Build-Depends to Build-Depends-Indep is also one of the least disruptive ways to make a Debian source package cross-compilable in cases where build dependencies that do not work in a cross-context are only used to build the arch:all packages. https://wiki.debian.org/CrossBuildPackagingGuidelines#Declare_.22Indep.22_Build-Dependencies Moving stuff to Build-Depends-Indep also helps the architecture bootstrap use-case as arch:all packages do not have to be bootstrapped for a new architecture and the fewer build dependencies remain in Build-Depends or Build-Depends-Arch the fewer build dependency cycles remain. Thanks! cheers, josch
signature.asc
Description: signature
