the first commit fixes the issue that PostInstallCob4.sh was not usable anymore on robots which haven't been set up with the latest images_config, i.e. kickstart-robot.sh
the second commit lists the function names that should have been executed during kickstart-robot.sh so the user (executing PostInstallCob4.sh) is able to determine whether all steps are actually applied to his current robot...
I played around with export and declare to be able to actually call (selected) functions from the kickstart-robot.sh....however, kickstart-robot.sh would need to be sourced within PostInstallCob4.sh....but then some steps would already be executed...
what's more, the steps in kickstart-robot.sh are implemented to run on a single PC during setup and not to be executed without sudo and on all** PCs....and I don't want to mess around in this script...
thus, listing the functions from kickstart-robot.sh is IMHO the best thing atm we can do to remind the user to check...
the first commit fixes the issue that
PostInstallCob4.shwas not usable anymore on robots which haven't been set up with the latest images_config, i.e.kickstart-robot.shthe second commit lists the function names that should have been executed during
kickstart-robot.shso the user (executingPostInstallCob4.sh) is able to determine whether all steps are actually applied to his current robot...I played around with
exportanddeclareto be able to actually call (selected) functions from thekickstart-robot.sh....however,kickstart-robot.shwould need to be sourced withinPostInstallCob4.sh....but then some steps would already be executed... what's more, the steps inkickstart-robot.share implemented to run on a single PC during setup and not to be executed withoutsudoand on all** PCs....and I don't want to mess around in this script...thus, listing the functions from
kickstart-robot.shis IMHO the best thing atm we can do to remind the user to check...