DEV Community

loading...

Discussion on: Advanced usage of yum-config-manager with setopts

Collapse
ferricoxide profile image
Thomas H Jones II

Usually, just installing the -release RPM takes care of things like any necessary GPG key-imports. Our primary usage of yum-config-manager is when a third-party repository needs to be permanently enabled (and the release-RPM doesn't default to enabling the installed repository definition(s)).

Collapse
rndmh3ro profile image
rndmh3ro Author

Usually, just installing the -release RPM takes care of things like any necessary GPG key-imports

Yeah, usually. However with Ansible (or our self-created repos) that's not always the case, sadly.

Our primary usage of yum-config-manager is when a third-party repository needs to be permanently enabled (and the release-RPM doesn't default to enabling the installed repository definition(s)).

That's a good use-case, too!

Collapse
ferricoxide profile image
Thomas H Jones II

When you build your self-created repos, you don't include the requisite verification keys' installation and enablement within the release-RPMs that define those repos to your client systems?

Thread Thread
rndmh3ro profile image
rndmh3ro Author

Well, with "our repos" I meant our companies repo's, managed by someone else who does not do this. So - yeah.

Thread Thread
ferricoxide profile image
Thomas H Jones II

My condolences. Seems the number of people that know how to maintain a custom yum repository hosting custom RPMs is quite small ...smaller, even, than the already small number of people that know how to create RPMs (let alone properly sign one).