On Wed, Aug 05, 2020 at 10:50:59PM -0400, Stephen Gallagher wrote:
On Wed, Aug 5, 2020 at 6:17 PM James Cassell
<fedoraproject(a)cyberpear.com>
wrote:
>
> On Wed, Aug 5, 2020, at 3:36 PM, Stephen Gallagher wrote:
> > * If a stream of a module has build-time-only components, all such
> > components *MUST* be marked as `buildonly: True` in the module
> > metadata to avoid shipping them to users and polluting their
> > repository.
> >
>
> Can these be directed to a disabled-by-default build-dep repo of some kind
> for those trying to do local builds?
>
That's not really a policy question, but it's *possible* that we could
do that as part of the compose. I don't see a lot of reason to do so,
since a local MBS build will handle it for you and as we establish
later on, the use of these should be a last resort, not a common
practice.
These build-only components are handy for running tests after the build.
E.g. a non-build component has upstream tests. They are run at build-time, and
thus the module contains build-only components for performing the test. The
tests are also packaged into a subpackage and the subpackage is filtered from
the module. ("buildonly: true" is only a different form of "filter"
modulemd
section.) Later a CI may want to install the subpackage and reproduce the
tests.
-- Petr