Me: why does this Yocto setup script keep failing on not having a pre-existing bblayers.conf, this is dumb, why is this dumb?!
I finally shoved enough debugging in and found:
("OpenEmbedded requires 'python' to be python v2 (>= 2.7.3), not python v3.n"<br></br> "Please set up python v2 as your default 'python' interpreter.")<br></br>
which explains why it's not working on a system that only has python3.
Ok lets go see if I can pull in a newer version of that and NOT break everything under the sun doing it
This might sound silly, but I installed virt-manager to make things a little easier when using qemu, then created a new virtual machine with debian 12 on it... then installed qemu on that.
The actual reason for this is to make github account separation a little easier...
If you get virt-manager set up properly, it definitely makes using qemu easier, though. I practically just had to tell it to make a new virtual machine using this iso with this much memory and this big of a hard drive, and it was right at the debian install screen. (Set it up with xfce...).
Main tricky parts were that I had to install libvirt first, make myself a member of the libvirt user group, enable the service, and install dnsmasq. Not great, but could've been worse...
Used debian on the virtual box just for a little variety. I like to keep my hand in on different distributions a bit.
But speaking of OS/1337, i really need to get crackin' on those open issues and start using the reworked scripts of yours so my old mess can get yeeted sooner than later...
Thanks again to @SweetAIBelle for extensive contributions to OS/1337, making the pipeline and scripts to reproduceably build OS/1337 images and it's parts more flexible and nifty.
@SweetAIBelle I think this is great forward-thinking on your side since OS/1337 should long-term be developed into a robust yet "clean slate" for #minimalist#Linux that isn't as bloated as #Yocto but remains customizeable and flexible.