Perhaps conditionally on cross only? I'm not too fond of the rebuild amount at this stage, if it improves basically nothing (on those rebuild platforms).

Thanks. I agree, made it conditional for now.

I'm a bit afraid to last-minute merge this, altough the breakages should be minimal.
Maybe we should wait until the branch-off (this evening european time), target staging with this and assign the backport staging-22.05 label?

This should have the same effect as the previously added STRIP= in makeFlags, as far as I can tell (didn't research in any way, but strong assumption), the flag was just renamed from STRIP to STRIP_OPTS.

Since it's now conditional on cross-compiling, it shouldn't affect any native packages.

I don't really mind if we do this now or after the release (possibly with a backport). If we do it after the release I will make it unconditional again. I'm not in a rush. But I saw it broke on staging-next where master was fine, and I'm trying to keep cross regressions low.

Yes, the effect is cross-only (including rebuilds), and even there it doesn't seem risky.

After talking to @mweinelt, it seems to be a good idea to target master with this PR and to merge it once staging-next is in, backporting this to release-22.05.
This way we can skip staging altogether because it's not a mass-rebuild anymore.

I don't mind either as it doesn't cause rebuilds on hydra anyway.

It's only targeted at staging-next because it's only needed after the update that's in master..staging-next now.

Alright, then