> > > > Wouldn't this cause a reboot loop? The enable and disable package both > > need an immediate reboot... > > One could set an environment variable to avoid this, which gets checked > to prevent the execution of the install commands. > > The reboot loop problem exists with the first solution presented to the > OP too. >
Does it? First Boot: the <condition> says FBWF is on, so FBWF gets disabled and an the system boots immediately (<exit code='bla' reboot='true/>) Second Boot: the <condition> for the disable command checks if it is already disabled. If it is disabled - no reboot -> packages get installed. Then the Prio-0 Package installs last, enables FBWF, reboots. Third boot: No packages scheduled for install - so FBWF won't be disabled and prio0-package won't get installed (because it is execute=change). System boots normal. Of course getting this bug-free is a challenge (one bad package def will cause a reboot loop) - but i think it's possible.
------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
