Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packager v3: Extend configurations to allow stream renaming #599

Open
sgallagher opened this issue Jul 25, 2022 · 3 comments · May be fixed by #601
Open

Packager v3: Extend configurations to allow stream renaming #599

sgallagher opened this issue Jul 25, 2022 · 3 comments · May be fixed by #601

Comments

@sgallagher
Copy link
Collaborator

It would be useful to add an optional stream: key to the data.configurations section of the Packager v3 format. This would allow us to submit the module with a custom stream name for certain contexts.

As a real-world example, I currently maintain a variant of the 16 stream for EPEL 9 called 16-epel which is needed because the RHEL module does not provide v8-devel, needed for some EPEL packages. Right now, I have to maintain a completely separate branch in dist-git, despite the modulemd being essentially identical except for the stream name. It would be much more convenient to have an override in the configurations section instead.

@ppisar
Copy link
Collaborator

ppisar commented Jul 26, 2022

In other words you want to build multiple streams from a YAML file stored in a single dist-git branch.

While technically possible, there are two issues with it:

@sgallagher
Copy link
Collaborator Author

  1. MBS already supports doing this for the stream, since in RHEL we set the stream name because it comes from a differently-named branch. It would be fairly easy to add this to the ModulemdPackagerV3.convert_to_index() function.

  2. The Fedora policies can be updated once new functionality is added.

sgallagher added a commit to sgallagher/libmodulemd that referenced this issue Jul 26, 2022
@sgallagher sgallagher linked a pull request Jul 26, 2022 that will close this issue
@ppisar
Copy link
Collaborator

ppisar commented Jul 27, 2022

I'm not sure that MBS processes a stream value only after converting modulemd-packager into modulemd. When I wanted to add a similar feature for overriding component refs by context, I found out that MBS processes refs before the conversion.

I do not want to add yet another feature into libmodulemd which will be kept unimplemented by MBS. Like default profiles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants