If it doesn't need to access root files, you install it inside a container.
toolbox create
toolbox enter
Takes just a few seconds and now you're inside a traditional Fedora 40 CLI system that can access your /home but otherwise has a separate file system. This is great for setting up a dev environment without polluting the host system.

If it does need to access root files, you can install it with rpm-ostree, which basically creates a new OS image that contains the app.
rpm-ostree install --apply-live [package name]
But if you feel like you need that a lot, a traditional Linux system would be a better fit.

The way I use Silverblue is kinda like Android. All the apps I need for my general purpose laptop are available as flatpaks. The OS itself kind of disappears in the background. I set it to update itself automatically without telling me and I actually don't do anything with the terminal or outside of /home . The OS is a GUI application launcher, which is exactly what I was looking for after 20 years of tinkering with Linux.

[–] lambda@programming.dev 2 points 2 months ago

Thanks for the input! I'll look more into these

[–] subtext@lemmy.world 2 points 2 months ago (1 children)

They recommend using brew to install CLI apps. There are also dev containers and toolbx, but the latter is not recommended.

https://universal-blue.discourse.group/docs?category=6

[–] lambda@programming.dev 2 points 2 months ago

Huh, I thought brew was a Mac thing. Thanks for the link. I'll give it some reading.

[–] barsquid@lemmy.world 1 points 2 months ago (1 children)

You typically do that in a container and use the container.

If you really want it on your system root you can layer it in as a commit on top of the distro with rpm-ostree. System upgrades should change the commits below yours but keep your modifications on top.

[–] lambda@programming.dev 1 points 2 months ago (1 children)

So, if I wanted to install zsh I would need to use a container for it?

[–] barsquid@lemmy.world 1 points 2 months ago

For something like that where you likely want it everywhere, I would probably layer it on top of the base system (with rpm-ostree install zsh). That uses the same Fedora package management as dnf but applies it as a changeset on the immutable system instead of modifying things directly.

Something more specific to a single category of task (I'm thinking like Rust or Python tooling) you might want to leave in a container.

[–] KISSmyOSFeddit@lemmy.world 3 points 2 months ago* (last edited 2 months ago) (2 children)

What's the difference between Bluefin and Silverblue?
I was interested in the Ublue images but it sounded like Silverblue is kind of the "default vanilla favor" and the Ublue images stack more stuff on top or modify it for special use cases. So I'm now on Silverblue, and it's pretty fucking awesome as a "forget it's even there" general purpose laptop OS so far.

[–] barsquid@lemmy.world 3 points 2 months ago

That's my understanding also, ublue are adding some different default software/settings and maintaining versions specifically with Nvidia and/or ZFS support.

[–] subtext@lemmy.world 2 points 2 months ago (1 children)

It’s basically Silverblue but with all the nice to haves already built in. They try to make it extremely user friendly for install and then just using it without tweaks or having to add anything yourself

[–] KISSmyOSFeddit@lemmy.world 2 points 2 months ago (1 children)

I made the right choice then. The only thing I changed on Silverblue was hiding the pre-installed Firefox and replacing it with the Flathub version that includes non-free codecs.
And I was surprised to see it's missing gparted and gnome-tweaks, but I work around that with gnome-disk-utility and dconf-editor.

[–] subtext@lemmy.world 2 points 2 months ago

More power to you! To each their own, I prefer most of the tweaks that Bluefin did and they make it pretty easy to turn off some of the more controversial ones.