Collection of Module Streams with the same name.
Default Module Stream
Default Module Stream is a <<Module Stream>> pre-selected by the software distributor (such as Fedora or RHEL authorities) to be implicitly considered for package installation and dependency resolution and automatically enabled when packages from the stream are needed. One Module can only have zero or one Default Module Stream.
Example: The nodejs:14 <<Module Stream>> is the Default Module Stream of the nodejs <<Module>> and the stream contains a libuv package. When the user installs libuv (directly or indirectly), the nodejs:14 <<Module Stream>> is automatically enabled without an explicit user action. Installation of the libuv package from any other <<Module Stream>> or from a non-module repository requires explicit action (such as disabling the nodejs:14 stream).
For example: postgresql module consists of postgresql:10 and postgresql:12 <<Module Strea,Module Streams>>. “Module” is also frequently used as an informal reference to <<Module Artifact>>. For example: Hey buddy, I’ve just built the postgresql:12:20200101:aabbccdd:x86_64 module, go check it out!
For example: you can specify that mariadb:10 can be built for f29, f30, f31 and not built for f28 with specific options for each buildroot.
For more information see xref:architecture/nsvca.adoc[this section].
For more information see xref:architecture/stream-expansion.adoc[this section].
For more information see xref:building-modules/fedora/defining-modules.adoc[this topic].
Modularity introduces a lot of new keywords to the established packaging ecosystem. This is a short glossary to get you started on the basic terms.
Modularity is an extension to the RPM ecosystem that allows to distribute and consume <<Module Repository,Module Repositories>> with alternative content.
Module Artifact
Module Build
Module Build is a collection of <<Module Artifact,Module Artifacts>> with the same <<NSVCA,NSVC>>
Module Metadata is a modulemd yaml document that contains information about a <<Module Artifact,Module Artifact>>. Module Metadata can be found in modules.yaml in the repodata.
Module Metadata (modulemd)
<<Module Metadata (modulemd),Module Metadata>> + built RPMs identified by <<NSVCA,N:S:V:C:A>>.