> Does anybody know how to add this "SOFTWARE SELECTION" section to the i3
> spin Anaconda installer? Then the base i3 spin could be minimal, and
> there could be a couple options with progressively more stuff thrown in
> such as:
>
> * nothing - don't install anything extra
> * minimal - add things such as xss-lock (ie. things recommended in the
> default i3 config)
> * functional - add things that a typical user would want (ie. thunar,
> firefox, bluetooth)
> * full - rice it up (ie. music player, calendar, etc.)
No idea if that's possible, but it would be nice.
I'm working on this but pointing to F36. Why? Because we have a lot to do for F35 and it won't be feasible.
If anyone can take the task outside the "core" team (there is no such thing, but only 5 people are constantly showing in meetings)
> Also, I have been experimenting with using flatpaks instead of .rpm
> where it makes sense, and so far the results seem pretty good. I guess
> the use of flatpaks will trend up over time. But it does introduce the
> complexity to spins regarding what would be an rpm (ie. i3status,
> xss-lock, probably thunar, etc. - basic utilities that make the system
> work) and what should be flatpak (ie. firefox, music player, etc. -
> desktop apps that the user interacts with for work or amusement). Is
> there even a way to install flatpaks during install? Is this something
> that should be considered, or should flatpaks continue to be completely
> ignored in favor of a 100% .rpm install?
I am not 100% sure, but I don't think that Anaconda allows you to
install flatpaks (searching for flatpak in the docs yields no
results[1]).
AFAIK no. Only way should be doing something similar to Kionite, rebasing Silverblue and from there build the image.
Again, thanks for taking the time to comment, every comment enrich us.
Br,
--