Work around for common Fedora dev toolchains?
I'm switching to linux to get away from Windows. Bazzite has been awesome so far but it's time to write some software for it.
I've come to learn that this is rather unsupported as the OS is mainly read-only and I'm not even super-user!
Ok there's some sense there and I appreciate the simplicity, but sometimes I need tools I cannot get through
brew or flatpaks.
In the mean time, I have used the rpm-ostree command to install a few developer libraries with success (I'm taking risks I know), but not everything can be found via rpm-ostree and are mostly available in Fedora's package manager dnf.
Is there a way to elevate my privileges? Are there recommended alternatives to installing common dev tools on Bazzite?
It would be great to be able to develop on the same OS I'm using in order to support the user base and the Bazzite ecosystem.Solution:Jump to solution
Rebase to bazzite-dx and keep development libraries in distroboxes (instead of rpm-ostreeing stuff, use dnf in a fedora distrobox and develop/compile/etc in there)
2 Replies
Solution
Rebase to bazzite-dx and keep development libraries in distroboxes (instead of rpm-ostreeing stuff, use dnf in a fedora distrobox and develop/compile/etc in there)
I just tried out
distrobox and it seems like exactly what I should have used to begin with.
To those reading this, it creates a contained environment using only the tools and libraries installed with that active distrobox while providing an opaque shell to your local files. In this way you can freely enter distroboxes and install toolchains without polluting root and still develop on (or for) Bazzite.