This PR adds ability to include modules in the packages section, which will install them (i.e. install all RPMs listed in the default profile for the module stream, the equivalent of dnf module install …). A new top level key moduleEnable can specify which modules should be enabled (i.e. packages made available for installation, but nothing gets installed directly; the equivalent of dnf module enable …).
Enabled modules need to be combined with listing the desired packages in the packages section.
Here's an example. Imagine three module streams providing some package:
m:1.0 has foo-1.0
m:2.0 has foo-2.0
m:latest has foo-3.0
The latest stream is configured as default.
If the input file contains packages: ["foo"], the lockfile will end up with version 3.0, since that's the default.
By adding moduleEnable: ["m:1.0"] (or 2.0), you can tell resolve the lockfile for a different version.
This PR adds ability to include modules in the
packagessection, which will install them (i.e. install all RPMs listed in the default profile for the module stream, the equivalent ofdnf module install …). A new top level keymoduleEnablecan specify which modules should be enabled (i.e. packages made available for installation, but nothing gets installed directly; the equivalent ofdnf module enable …).Enabled modules need to be combined with listing the desired packages in the
packagessection.Here's an example. Imagine three module streams providing some package:
m:1.0hasfoo-1.0m:2.0hasfoo-2.0m:latesthasfoo-3.0The
lateststream is configured as default.If the input file contains
packages: ["foo"], the lockfile will end up with version 3.0, since that's the default. By addingmoduleEnable: ["m:1.0"](or 2.0), you can tell resolve the lockfile for a different version.