Why is it unneeded? I suspect it's useful if someone locally layers chrome rpm. @tpopela, any comments?

I'd argue that if you layer the chromium package then the config should be pulled as a dependency. But maybe having the option of removing the config and thus not having it as a dependency was the idea. I don't have strong arguments for this one.

This came from https://discussion.fedoraproject.org/t/intention-of-fedora-chromium-config-in-base-image/28261

This package is there to make sure chrome users get their user agent correctly set to fedora when downloading chrome directly from google. Note that I'm talking about chrome, not chromium -- we don't control chrome dependencies as it's downloaded from a third party.

The package predates soft deps in fedora though. I think these days it should be possible to use 'Supplements: google-chrome-stable' in fedora-chromium-config to inject a reverse soft dep to pull the package in when installing chrome. (And likewise with google-chrome-beta or something, not sure what the non-stable chrome packages are called.)

It's up to tpopela though :) I think it's best to keep the package on the install media for now as it currently doesn't have the reverse deps set.

Hi @siosm, yes kalev is right - the package has two specific reasons:

a) preinstall the Chrome/Chromium extension that we use to change the User Agent to contain Fedora

b) It ships the necessary policy files so the kerberos integration works out of the box on Fedora sites (that are using FAS).

From my POV, the package should stay.

Thanks for the explanation!