On 2011/6/20 Dan McGee <[email protected]> wrote: > This sucks a bit, but is a big failing of netcfg I found when writing my next > patch. It screams "there must be a better way", but at the moment I'm not sure > what that may be. The biggest problem is there is no central collection of > these variables which I had to scrape from the various setup scripts. > Thoughts?
I'd better say we should enforce the use of subshells whenever multiple profiles are expected to be loaded in a sequence. For example; by making load_profile a hard failure if $DESCRIPTION (or any other common variable) is already set. Rémy.
