I noticed recently that Kate was included in the default packages for Kinoite’s base image; I don’t think it was always there. Then I noticed today that it is being removed with today’s base image update.
Just curious where the discussions are taking place in regards to what gets added/removed from Kinoite. Just for curiosity’s sake, I want to find out about possible upcoming changes and the thought processes behind them. Thanks.
The addition or removal of packages are not always intentional, it is sometimes also triggered by a transitive dependencies. The Fedora Silverblue and Kinoite composes are built every day on the Fedora Infrastructure. There is a config file that have base packages defined, and the compose contains these packages and all transitive dependencies. So for example if package A is described in the config file and package A depends on package B, and package B depends on package C, the A, B, and C packages are in the compose. But when package B no longer need package C, the next compose will not include package C so you will see that package C is removed on next update because rpm-ostree shows you a diff between two composes on the end of upgrade. For example there was an bug in Fedora Silverblue caused by a transitive dependency reported by me: https://github.com/fedora-silverblue/issue-tracker/issues/127
We discuss Kinoite issues/enhancements in the KDE SIG issue tracker, with the Kinoite label: Issues - fedora-kde/SIG - Pagure.io
For Kate, the addition was not intentional but the result of dependency changes in packages. Once the dependencies got fixed, it was auto-removed. I did not have the time to investigate it so I left it there.
We also share a lot with Silverblue so sometimes package additions are discussed in the Silverblue issue tracker too: Issues · fedora-silverblue/issue-tracker · GitHub