search

fedora-copr / copr

RPM build system - upstream for https://copr.fedorainfracloud.org/
115 stars 59 forks source link

Put modules into the main project repositories #1576

Open fedora-copr-github-bot opened 1 year ago

fedora-copr-github-bot commented 1 year ago

Original issue: https://pagure.io/copr/copr/issue/1576 Opened: 2020-11-19 06:59:57 Opened by: praiskup

Currently, when module is built - we create a separate directory for the moudule (separate createrepo_c run).

Modular repositories should be merged with the main repository, and and each chroot should have only one repo - similarly like the RHEL AppStream repository (it contains both modules and normal packages, and modules can be listed and enabled if user wants).

frostyx commented at 2020-11-19 12:59:19:

Agreed, I wanted to do this for a long time

FrostyX commented 1 year ago

Modular repositories should be merged with the main repository, and and each chroot should have only one repo

Actually, I think they shouldn't be merged to the main repository but each module should be placed into its CoprDir. That way we can safely have module and non-module packages in one projects and still ensure upgrades between module versions within one repo.

But maybe merging into the main repository might work as well, we should investigate before implementing.

praiskup commented 1 year ago

Hmm, isn't modular content meant to be "optional" itself? Like, I dnf install foo, but modular foo is not installed unless I explicitly dnf module enable? Can you elaborate on the benefits of "ensure upgrades between module versions within one repo"?