Hi Helmut, > Explanation: The nocheck build profile is used to disable binary > packages from being built while the profile is expected to not vary > the resulting artifacts at all. There is a use case for skipping > the installation of benchmarks, samples and test programs and it is > served by the noinsttest build profile.
You're likely aware that this is already implemented and merged, but thinking more about it, I feel the wording below is a bit confusing or even wrong. > If a build dependency is > required for running build-time tests or installed tests, it should > be annotated <!nocheck> <!noinsttest>. Then it can only be skipped > when supplying both profiles at the same time. This gives the impression that every single build dependency that is used for testing should be annotated with both of !nocheck and !noinsttest. This seems incorrect? My understanding is that it is applicable for only the cases where tests are built at runtime _and_ also installed as a (separate) binary package. If it is just a build-test dep without installing the tests, just !nocheck should be enough. Do you mind rewording this and sending across a MR? I'll be happy to quickly merge that. Best, Nilesh
