Wow This stuff looks awesome! I think it covers almost everything I could hope for in an installer; the only thing left is - would it be possible to generalize one step further up to selecting the DE, then the core/gaming/office/etc options?
This leverages shell scripting and https://github.com/TomWright/dasel to read the list of packages to install in ublue-firstboot and the containerfile. If in the future another firstboot solution i...
What yall talked about with the composability / eating our dogfood sounds fantastic, especially as the current selection of non-nvidia images feels very GNOME-oriented.
Yeah, I locally built the image and everything seems to work. Just can't figure out how to rebase without it being in a registry. Don't know why the push fails, thought that was intentional. I don't think anything I changed should affect that.
Interesting! The idea occurred to me for two reasons:
- There were already a lot of parallel images, then when I mentioned steam-devices y'all went from it to udev rules to all udev rules to codecs to app bundles to a modular repo system, and the potential image count/complexity ballooned. A unified installer seemed like a great way to manage that complexity in the user space. If you offer base, Silverblue, Kinoite, Vauxite, and two or three more options, that last one dramatically cuts the chance that someone will ever choose any of them over another distro. Big hazard in marketing and the psychology of decision making in general. One installer for all of them with no-selection defaults alleviates it
- Regardless of necessity, it's a relatively "simple" type of feature which at least Windows if not Mac users expect, and it's a lot less imposing as a first step than working from the command line. I would hope that it somewhat bridges the gap of what users somewhat arbitrarily think of as polished and indicative of a consumer-ready operating system due to familiarity and availability heuristics
Also - never before have I seen OS devs move a tenth so fast to address usability concerns, UX, and reliability. It's already made a huge difference for me personally, and it's exactly the sort of thing I aspire to and built my major around. I really appreciate it and I look forward to having time to contribute more directly
We're able to move fast because we're leveraging some of the best features of containers, which is making a build system that's relocatable, easy to offload onto other hosts, can be structured in whatever makes the most sense for our needs, and is easy to normalize with one pull spec composing an entire file tree compared to having to test against any number of package configurations
I absolutely agree with jstone, but appreciate your sentiment. This wouldn't have really been possible 2 years ago - it's right at the edge of a tipping point in how we build desktop distros
Canonical's take: "what if we deployed a distro as a bunch of containerized images that get updated side-by-side?", Silverblue's take: "what if we deployed a distro as one containerized image that gets updated in one place?"