data/profile.d: Add profiles for KDE & Kinoite Spins

[travier]

Both profiles are based on Workstation but use the generic Fedora Linux
branding until we make specific ones for those two spins.

Fedora Kinoite is a new Fedora variant similar to Fedora Silverblue,
introduced in Fedora 35.

See https://fedoraproject.org/wiki/Changes/Fedora_Kinoite

[travier]

Marking as draft as I'm not sure exactly what impact this would have.

[poncovka]

It seems reasonable to use configuration defaults of Fedora Workstation. It will hide some configuration screens in the summary hub and change the look of the user interface. See: https://github.com/rhinstaller/anaconda/blob/master/data/profile.d/fedora-workstation.conf

Could you please add a test for this profile in the test_fedora_profiles function of the ProfileConfigurationTestCase class? It will start to validate the configuration file.

If you want this change in F35 Beta, you will need to report a bug for Anaconda and ask for an exception. If you want it in F35, we will need to port it to f35-devel branch.

[poncovka]

/kickstart-test --testtype smoke

[VladimirSlavik]

Looks good to me. Thank you!

[Conan-Kudo]

You don't want to do this, we don't have an equivalent to gnome-initial-setup yet to make this work. That's why we haven't done it yet.

[travier]

Hum, is initial-setup-gui not enough?

[Conan-Kudo]

That's controlled by the Anaconda configuration. So it's just broken.

[travier]

That's controlled by the Anaconda configuration. So it's just broken.

Any pointer to what needs fixing so that I can take a look?

[poncovka]

That's controlled by the Anaconda configuration. So it's just broken.

Any pointer to what needs fixing so that I can take a look?

There was no use case for that so far, we need to figure out how to approach the issue. As a temporary workaround, we could reset the hidden_spokes option in the initial setup configuration file. See: https://github.com/rhinstaller/initial-setup/blob/master/data/10-initial-setup.conf

[poncovka]

Actually, the initial setup doesn't use VARIANT_ID to load profile configuration files. It uses only ID, so I don't understand how it is broken. It should use the fedora configuration profile for all variants of Fedora. See: https://github.com/rhinstaller/initial-setup/blob/1ba27b4d9db7de2a46e5f208cdab65efb07c927a/initial_setup/__init__.py#L110-L112

[M4rtinK]

There was no use case for that so far, we need to figure out how to approach the issue. As a temporary workaround, we could reset the hidden_spokes option in the initial setup configuration file. See: https://github.com/rhinstaller/initial-setup/blob/master/data/10-initial-setup.conf

Agreed - maybe have initial setup specific variant of hidden_spokes so that both can be set separately?

And in general, I agree this is something Initial Setup should handle & I'm ready to help as Initial Setup maintainer.

[travier]

OK, I've updated this one to mirror the workstation settings while keeping things independent until we figure out where we can share more.
As I don't think this will change much for F35, let's keep it for master only and I'll try to work on fixing the initial setup issue. Tracking issue: rhinstaller/initial-setup#136

[poncovka]

/kickstart-test --testtype smoke

[poncovka]

Agreed - maybe have initial setup specific variant of hidden_spokes so that both can be set separately?

That makes zero sense. I am not going to support two versions of configuration options. If we are not able to use Anaconda's profiles in Initial Setup, then Initial Setup should have its own profiles.

[poncovka]

Actually, the initial setup doesn't use VARIANT_ID to load profile configuration files. It uses only ID, so I don't understand how it is broken. It should use the fedora configuration profile for all variants of Fedora. See: https://github.com/rhinstaller/initial-setup/blob/1ba27b4d9db7de2a46e5f208cdab65efb07c927a/initial_setup/__init__.py#L110-L112

It means that #3577 (comment) is not true and you can set hidden_spokes in your profiles, because Initial Setup won't use them. The current support should be sufficient for your use case.

[travier]

I think this one should be ready. I will try to work on the suggestion from rhinstaller/initial-setup#136 (comment) in a different PR.

[poncovka]

Thanks!