installoptionalpackage cul-de-sac if first run was netless
|Reported by:||jonas.kirilla||Owned by:||mmadia|
|Component:||Applications/Command Line Tools||Version:||R1/Development|
One might not always have networking set up on first use of installoptionalpackage: router turned off, cable unplugged, .. This makes the script fail at doing anything meaningful - no suprise - but it results in an empty OptionalPackageNames file which blocks all subsequent runs.