Modularity allows users to choose a specific version of an application and receive updates for it. Modules act like views of a repository, hiding certain parts from the package manager. A typical workflow involves adding a modular channel, creating filters for needed modules, and building the project, with dependency resolution handled by a Python module that automatically adds dependencies to the repository.

1. cbbayburt@suse.com

2. Modularity enables you to choose a particular version of content, and to
receive the right updates for it.
● A single line of updates for a single major version of
an application, shipped with the distribution.
● Parallel lines of updates (streams) selectively enabled
for multiple versions of an application.
Modules act like projected views of a repository, hiding parts of it from the
package manager.

3. ● Implemented as AppStream repository in CentOS/RHEL
● Modules are implemented in an extra metadata file called
● The package manager can still be used the old way

4. ● Implemented as AppStream repository in CentOS/RHEL
● Modules are implemented in an extra metadata file called
● The package manager can still be used the old way

5. A typical CLM project workflow:
1. Add a modular channel as a source

6. A typical CLM project workflow:
1. Add a modular channel as a source
2. Create AppStream filters for each module needed

7. A typical CLM project workflow:
1. Add a modular channel as a source
2. Create AppStream filters for each module needed
3. Build the project

8. Modular dependency resolution is handled by a Python module called
‘mgr-libmod’.
In the process, any dependency modules will be added to the repository
automatically.

9. ● Will modular repositories be fully integrated at the core level?
● How do I add all the modules effortlessly?