It depends on what your metrics are for energy and resources. Are you talking about the end user hardware, or are you talking about developer time and effort. If it’s the former, you’re right, if it’s the latter you’re completely wrong. And while there’s merit to your point (if it is about end user storage, energy consumption, etc), that’s not really in short supply while open source developers free time is.
https://www.urbandictionary.com/define.php?term=Thirsty
https://www.urbandictionary.com/define.php?term=thirst traps
The author isn’t using thirsty, like you’re thirsty for water. They are using the slang version.
I can see how you would misunderstand without knowing that.
Is there a specific part that you’re having trouble with? Is it more how it works under the hood, or more about using it to spin up containers? I can try to answer any questions and post some how tos for you.
This documentation is for bazzite, but they have a lot of the same stack under the hood. “Broadcom’s WL driver can be installed since it is needed by some hardware. Disabled by default. Enter “just use-broadcom-wl” to use it.”. You could try to see if aurura has the same “just” options, that’s where I would first research. If not, then yeah, “rpm-ostree” would be how you install the package, just like you said, just not sure of the commands for local files. Also there is a tool to “roll your own” distro built on top of any of the ublue work, it’s basically how bazzite and aurora exist. So you can layer the packages like the other option you said. https://github.com/ublue-os/image-template