[wpkg-users] Disable FBWF before installing software

Stefan Pendl stefan.pendl.71 at gmail.com
Fri Nov 16 09:12:23 CET 2012

Am 14.11.2012 18:24, schrieb heiko.helmle at horiba.com:
>  > >
>  > > 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.

Sure there will be the need to include a flagging system to prevent a 
reboot loop, but that is needed for both ways.

One will have to decide which way is adding less to the overall amount 
of maintenance of the packages.

I myself would not want to have the same type of code in all of my packages.
Sure there are ways to automate this, like it is shown by the Firefox 
extensions, that use a common framework which gets filled in while the 
package is read.

Stefan P.

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

More information about the wpkg-users mailing list