Hello!
So I have decided to attempt to make my own image, and I have found the template on GitHub, read documentation etc.
A while ago I posted about having a Ujust script for Affinity and now that I looked at making my own image, it sounds like something I can set up when I make it.
The Ujust script would download the correct Elemental Warrior Wine into the Lutris runners folder, and use the Yaml file to instruct Lutris to use that version of Wine.
I tested a normal script and it worked, so I can potentially integrate that in a new image with ujust.
Then I could also make a ujust script for installing some Flatpaks I want like Discord, GPU Viewer, my browser or choice etc.
I have not decided if I want to layer Goverlay on top (I know at my own risk), or just add MangoJuice to the list of Flatpaks above.
I feel the above isn’t the best of reasons why I should make my own image, but it would allow me to practice making one. Mostly because one can just make scripts to install a bunch of Flatpaks, and could also just make a script to make the Affinity installation a tiny wee faster, and I have done.
Also let me see if I understood this correctly:
When making your own image you ARE still potentially overlaying rpm packages via rpm-ostree, but if there are errors, GitHub is better at telling you what the errors are and you can troubleshoot them before you swap to that image on your machine. GitHub makes a build (which I didn’t know it did, still new at this), and that’s how you troubleshoot it initially.
But if you layer rpm-ostree locally (on your machine), then if there is an error you have to rollback. If you have several rpm layers, you then have to figure out which one is not playing nice and why – info which is not really given to you locally.
The new GitHub image will pull the new changes Bazzite does upstram, and automatically rebuild my image periodically. You then know if your changes still play nice with the new Bazzite updates and if so, you are ready to update your own system.
Have I got this right?