artoo

Have't tested uefi since then.

I used the validation in check-yaml ``` $ check-yaml -cv --> Loading Packages: [Packages-Root] ... -> Writing Packages-Root-x86_64-openrc.yaml ... -> Checking validity [Packages-Root-x86_64-openrc.yaml] ... INFO - validation.valid --> Loading Packages:...

I switched yesterday to ruby-kwalify, it seem pykwalify has some bugs with schema validation and version depends, plus it won't accept *.conf files. ``` $ sh test.sh Validating data bootloader.conf...

@teo @philmmanjaro I think it would be useful to commit the schemas in the calamares source tree? However, it would be nice if the schemas and conf files were packaged...

I have looked a bit through the settings code, my rusty c++ asks the question, if it is possibly in c++ to serialize generated objects from yaml? @teo I was...

I don't mind putting them in hacking dir, but perhaps data is better? Anyhow, I can make our tools depend on a schema package, just tell final destination, we don't...

@teo I have moved the schemas temporarily in a separate repo. https://github.com/udeved/calamares-schemas I was wondering, perhaps have a git submodule pull them from eg calamares/calamares-schemas? This way you wouldn't get...

Would be very nice if upstream implemented writing displaymanagers to globalstorage. Right before last line's return in displaymanager main.py: ``` libcalamares.globalstorage.insert("displayManagers", displaymanagers) ``` I made it so that postcfg makes...

I have pushed both in calamares-manjaro. However, just this one line should go upstream and we drop our displaymanager. ;)

I can do PR for this one line upstream change, no problem. Once its merged, we drop the custom displaymanager module.