Some modules are built in MBS/Koji but are never released to users. Currently such modules can only be used as build dependencies of other modules. In future, if solution like "ursa-major" [1] is implemented, such modules could also be used as build dependencies for non-modular packages. An example of buildroot-only module is javapackages-tools. This module is used as build dependency for 4 modules, but it is not included in any compose and it's not shipped to users. Should such modules be considered as allowed in Fedora? I am not aware of any policy that would disallow them, but I would rather ask in advance and not be surprised if one day I find out that I have to ship such modules to users and support them.

On Tue, Aug 28, 2018 at 1:23 AM Mikolaj Izdebski <mizdebsk(a)redhat.com&gt; wrote: > Some modules are built in MBS/Koji but are never released to users. > Currently such modules can only be used as build dependencies of other > modules. In future, if solution like "ursa-major" [1] is implemented, > such modules could also be used as build dependencies for non-modular > packages. > > An example of buildroot-only module is javapackages-tools. This > module is used as build dependency for 4 modules, but it is not > included in any compose and it's not shipped to users. > > Should such modules be considered as allowed in Fedora? I am not > aware of any policy that would disallow them, but I would rather ask > in advance and not be surprised if one day I find out that I have to > ship such modules to users and support them. > This sounds absolutely fine to me.

Mikolaj Izdebski wrote: > Some modules are built in MBS/Koji but are never released to users. > Currently such modules can only be used as build dependencies of other > modules. In future, if solution like "ursa-major" [1] is implemented, > such modules could also be used as build dependencies for non-modular > packages. > > An example of buildroot-only module is javapackages-tools. This > module is used as build dependency for 4 modules, but it is not > included in any compose and it's not shipped to users. > > Should such modules be considered as allowed in Fedora? IMHO, no, why should that be allowed? If you think it through, it effectively means Fedora is no longer self-hosting. If you need a module to build your packages, you also need to make that module available to the users, if only to build their software.