The "commands" section of system.yaml
Just making sure I understand the role of the "commands:" section of the system.yaml:
1. I can place in there any custom commands that I need executed at system build time, right? Such as, say, "git clone," or "echo 'mask' > /sys/firmware/acpi/interrupts/gpe6E," or "flatpak install <list of flatpak packages to be installed>" etc.? Is that it?
2. What if some of these commands (such as the "git clone" above) must NOT be executed as root? Where do I place those?
3. Will these commands be executed every time the system is updated via akshara? What if I do NOT NEED these to be executed every time during update, as they may end up overwriting useful stuff that should not be overwritten?
1. I can place in there any custom commands that I need executed at system build time, right? Such as, say, "git clone," or "echo 'mask' > /sys/firmware/acpi/interrupts/gpe6E," or "flatpak install <list of flatpak packages to be installed>" etc.? Is that it?
2. What if some of these commands (such as the "git clone" above) must NOT be executed as root? Where do I place those?
3. Will these commands be executed every time the system is updated via akshara? What if I do NOT NEED these to be executed every time during update, as they may end up overwriting useful stuff that should not be overwritten?
Solution
@autisumn, @ﾑ丂ｲ乇尺ﾉ丂ズ: At any rate, I am tempted to conclude at this point that the
Many thanks for your attention to this matter though!
commands:system.yamlMany thanks for your attention to this matter though!
