diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2021-08-17 00:04:14 +0200 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2021-09-04 15:35:15 +0200 |
| commit | 017b3d0ae5232628c15324204e607e76487afb99 (patch) | |
| tree | 50b9467caa745a2bb14509fc730ab7af42192bc3 /test/integration/test-bug-990555-https-proxy-for-http | |
| parent | 902d114fce257fc1d51c510ac02de42b8ff1ec0e (diff) | |
Do not strip M-A for native build-dep resolution
Back than M-A was added to build-dependencies (#558104) only the
qualifiers :native and :any were considered at first which for the
native case behave the same, so stripping was a good idea.
Nowadays we could encounter arch-qualified dependencies, too, through –
or slightly more likely conflicts perhaps – at least in theory as in
practice native build-dep operations in Debian and elsewhere wouldn't
have other architectures available anyhow.
Still, we have full support for all this for the crossbuilding case
which makes active use of this (at least is far more likely to do so),
so it seems better to converge on one edgecase rather than keeping
two in active use and so produce potentially different results for not
specifying -a and -a $native.
Diffstat (limited to 'test/integration/test-bug-990555-https-proxy-for-http')
0 files changed, 0 insertions, 0 deletions
