Intention of fedora-chromium-config in base image?

Hello,

Does someone know the background/intention of including fedora-chromium-config in the base image despite shipping Firefox as the default browser?

rpm -ql fedora-chromium-config-1.1-7.fc33.noarch
/etc/chromium
/etc/chromium/policies
/etc/chromium/policies/managed
/etc/chromium/policies/managed/00_gssapi.json
/etc/opt/chrome
/etc/opt/chrome/policies
/etc/opt/chrome/policies/managed
/etc/opt/chrome/policies/managed/00_gssapi.json
/usr/lib/tmpfiles.d/fedora-chromium-config-tmpfiles.conf
/usr/share/chromium
/usr/share/chromium/extensions
/usr/share/chromium/extensions/hojggiaghnldpcknpbciehjcaoafceil.json
/usr/share/chromium/policies/managed/00_gssapi.json
/usr/share/google-chrome
/usr/share/google-chrome/extensions
/usr/share/google-chrome/extensions/hojggiaghnldpcknpbciehjcaoafceil.json
/usr/share/licenses/fedora-chromium-config
/usr/share/licenses/fedora-chromium-config/LICENSE
1 Like

It’s listed in Tree - workstation-ostree-config - Pagure.io from https://pagure.io/fedora-comps/blob/main/f/comps-f33.xml.in#_5456. We should probably exclude it. Will make a PR.

1 Like

PRs for F34+:

1 Like

See the discussion in the PR for the explanation for why this package is needed.

1 Like

Hmmm. I understand the intention, but it seems really odd to provide a configuration for a proprietary package like chrome (non-chromium) in a Fedora base image. Hopefully a reverse requirement can be implemented in the future.