fm-orchestrator

#469 RFE: Provide additional module metadata macros
Closed: Fixed Opened by psabata.

Closed: Fixed
Reopen Issue

When implementing RPM packaging changes, it can sometimes be useful to know the module name, stream name or perhaps even version. Consider extending the list of macros defined by module-build-macros with, for example:

  • %{_module_name}
  • %{_module_stream}
  • %{_module_version}

And possibly others.

Thanks. :thumbsup:

Metadata Update from @jkaluza:
- Issue assigned to jkaluza

Do you have an example of where you need access to this module data when building a rpm? I suspect we'd like to avoid embedding module-specific logic in specfiles (or at least make sure the module is buildable without it).

We already have %{_module_build} which we've used at least once already -- to weaken the strict NVR dependency between subpackages when splitting a build into multiple modules. It's also useful for testing packaging changes required by modularity that the maintainer is reluctant to include in the standard package right away.

I can imagine using these in the same conditional block in a similar manner to how %{fedora} and %{rhel} macros are used to day. Modules evolve, too :)

But I agree these shouldn't be used much. It's the last resort.

Metadata Update from @jkaluza:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/koji/mbs/issues/469

Please continue any further discussion there.
Metadata
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.