From 48b5145dd100548f4bc46691075cc95bf7ecabf6 Mon Sep 17 00:00:00 2001 From: Jiri Popelka Date: Nov 16 2023 10:09:08 +0000 Subject: perl:5.26 -> perl:5.32 to match the examples --- diff --git a/modules/ROOT/pages/core-concepts/module-dependency-resolution.adoc b/modules/ROOT/pages/core-concepts/module-dependency-resolution.adoc index e6b45f6..3f453f8 100644 --- a/modules/ROOT/pages/core-concepts/module-dependency-resolution.adoc +++ b/modules/ROOT/pages/core-concepts/module-dependency-resolution.adoc @@ -8,7 +8,7 @@ Module streams are groups of RPM packages which provide alternatives to the defa toc::[] -In the next couple of paragraphs we will try to explain how DNF is processing requests for enabling, installing and switching module streams. The first example below represents the state of a RPM repository on a fresh system. Nothing is installed from the RPM repository. The RPM repository is a modular RPM repository as it contains two module streams `perl:5.24` and `per:5.26`. It also contains some non-modular packages perl, perl-VSP, foo and bar. +In the next couple of paragraphs we will try to explain how DNF is processing requests for enabling, installing and switching module streams. The first example below represents the state of a RPM repository on a fresh system. Nothing is installed from the RPM repository. The RPM repository is a modular RPM repository as it contains two module streams `perl:5.24` and `perl:5.32`. It also contains some non-modular packages perl, perl-VSP, foo and bar. NOTE: The following examples are more a higher level overview how modularity works under the hood. For specific instruction how to use module streams with DNF check the section xref:using-modules.adoc[Using modules]. @@ -175,7 +175,7 @@ The only package which is not included in the `5.24` stream, but is also a non-m NOTE: Everytime you choose to add a module stream to your RPM repository it can be used to replace already existing non-modular packages when enabled and installed. Please always check if your module stream will not break your dependencies of your other installed software, after enablement and installation of your module streams. -The `5.26` stream is still available for enabling, but only one stream of the module name `perl` can be enabled at a time on a system. To be able to enable stream `5.26` we first need to reset and remove the installation of the `5.24` stream and all its packages. +The `5.32` stream is still available for enabling, but only one stream of the module name `perl` can be enabled at a time on a system. To be able to enable stream `5.32` we first need to reset and remove the installation of the `5.24` stream and all its packages. == Installing a module stream @@ -238,7 +238,7 @@ When a module stream is enabled you can install all the packages which are inclu == Switching a module stream [[example-4]] -_Example 4. state of the RPM repository when switching to 5.26 stream_ +_Example 4. state of the RPM repository when switching to 5.32 stream_ +++ @@ -291,7 +291,7 @@ _Example 4. state of the RPM repository when switching to 5.26 stream_
+++ -Before we can enable another module stream from the same module we have to first reset the already enabled module stream and remove it. In our situation in <> we have enabled the `5.24` stream of the `perl` module and installed it. To enable the `5.26` stream and install it we first need to uninstall all the packages from the `5.24` stream and reset it. +Before we can enable another module stream from the same module we have to first reset the already enabled module stream and remove it. In our situation in <> we have enabled the `5.24` stream of the `perl` module and installed it. To enable the `5.32` stream and install it we first need to uninstall all the packages from the `5.24` stream and reset it. The reset of the stream ensures that the state of the module stream in the DNF database is updated. Only after resetting a module stream, a new stream can be enabled and installed.