On 2022-09-17 10:25 +0800, Paul Wise wrote: > On Fri, 2022-09-16 at 19:53 +0200, Fab Stz wrote: > > > How does is this actually managed on the official buildd servers? How > > does it actually know which DEB_BUILD_PROFILES to apply on each run? > > The Debian buildds currently do not have support for build profiles, > for now build profiles are only for bootstrappers/porters/maintainers. > > It sounds like you are going to have to fix the upstream build system > to use the first build products during the second build product build. As Paul says, build profiles will not help here if you have to do this _every time_ you build the package, as opposed to doing it once, then using that to build the real package the first time in order to get it ready for the archive. i.e. build profiles are for bootstrapping, and the results do not end up in the archive. The normal way to fix this in Debian is for the debian build to run the build twice, using the components built on the first run for the second run. Can you do this easily, or do they have to be installed in system paths to work? You can also have the debian build run the build twice, one producing pkg-A and one producing pkg-B, so that both end up in the archive. Binutils is an example of a package that does this (building both native and cross versions). Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/
Attachment:
signature.asc
Description: PGP signature