> One thought: could we restore u to the hashbang and then just wrap the
> offending line in `set +u; ...; set -u`?
The offending line in clean_loops is in the functions file. If we have to change that, wouldn't it be better to use ${var-} instead of ${var} like I mentioned earlier? That seems closer to the intention of the code, which wants to know if a variable contains a path or not.
I may not be catching your suggestion, since I'm not a bash expert. If the above isn't the offending line you have in mind then please help me understand better.
> One thought: could we restore u to the hashbang and then just wrap the
> offending line in `set +u; ...; set -u`?
The offending line in clean_loops is in the functions file. If we have to change that, wouldn't it be better to use ${var-} instead of ${var} like I mentioned earlier? That seems closer to the intention of the code, which wants to know if a variable contains a path or not.
http:// bazaar. launchpad. net/~ubuntu- core-dev/ livecd- rootfs/ trunk/view/ head:/live- build/ubuntu- cpc/functions# L15
I may not be catching your suggestion, since I'm not a bash expert. If the above isn't the offending line you have in mind then please help me understand better.