Page Comparison

...

1. SIMP 6.6.0 requires RPMs from at least one module stream from epel-modular: 389-directory-server:stable, in order to support 389ds.

Conclusions

...

Requirements for SIMP ISO build + EL8 modularity

The following (derived from the In order information above) should enable us to build SIMP ISOs that distribute modular RPMs:

1. The ISO build process MUST distribute modular RPMs in “slim” subsets of their original module streams.

The alternatives are to include the entire modular repository (too big) or not ship dependencies (ISO is no longer self-sufficient)

1. In order to maintain seamless interoperability, each “slim” modular stream subset MUST use the same name + stream + version + context + architecture (N:S:V:C:A) as their upstream sources

2. If feasible, the “slimming” process SHOULD be generalized enough to apply to packages from external sources like epel-modular AND the base OS’s DVD AppStream/ repository.

2. The old createrepo command MUST NEVER be run on modular a repository

This applies to both the ISO’s build process and post-installation local tooling on SIMP systems.

1. Status
   colour Purple title TODO

   The ISO’s modular repositories MUST be built with modularity-aware tools, like createrepo_c or creatrerepo_mod from modulemd-tools.

2. Status
   colour Purple title TODO

   Local SIMP tooling MUST be changed to NEVER use createrepo to manage modular repositories:

...

3. “Slim” subset repos' modulemd metadata MUST remain intact when mirrored or rebuilt.

1. The modular repos MUST NOT be mirrored or rebuilt without it

2. The modulemd metadata will always be necessary in order to install these repos' modular packages—and once lost it cannot be recreated from their RPMs (unlike standard RPMs).

3. Status
   colour Purple title TODO

   Local SIMP tooling that mirrors modular repositories MUST preserve modulemd metadata (e.g., dnf reposync --download-metadata)

...