#171 RFE: UX for modules which replace packages in defined repos
Opened 4 years ago by mattdm. Modified 2 years ago

As a systems administrator, I want to distinguish between modules which contain alternate versions of packages which come from my base operating systems (including potentially modules in that OS).

I have use cases where I definitely do want to override that OS — I need something special for my application — but I never want to do to it without knowing that I may be putting myself in a situation where the people providing the base OS cannot support me and I will be relying on any support (community or otherwise) available from the provider of the module.

I'd like to be able to see this information before I decide to install a module, have it also noted while the module is installing, and additionally be able to produce a report after the fact.


Metadata Update from @psabata:
- Issue tagged with: needs-design

4 years ago

What's the difference from installing a non-modular package from a third-party repository which happens to overlay a package provided by the OS? People can follow repository name in "dnf install" output before confirming the installation. The same approach works for modules. I don't think your issue is specific to modules.

Login to comment on this ticket.

Metadata