Heiko's solution seems to make sense, it should work but then when I want to disable the FBWF manually, I would have to disable WPKG-GP too or it would be enabled and rebooted on next restart so I have to take that in account. I haven't had time to test but I will report as soon as I can. But about Stefan's remark, it would indeed be better to make a separate "disable FBWF" package which would be called from each of the original packages, but I don't think there's a way to do it currently or is there ?
Jonathan Verdeyen IT Engineer Automatic Systems S.A. - Avenue Mercator, 5 - 1300 Wavre - Belgique Phone: +32 (0)10 23 02 97 - Fax : +32 (0)10 23 02 02 www.automatic-systems.com Please consider your environmental responsibility before printing this e-mail. -----Original Message----- From: wpkg-users-boun...@lists.wpkg.org [mailto:wpkg-users-boun...@lists.wpkg.org] On Behalf Of Stefan Pendl Sent: vendredi 16 novembre 2012 09:12 To: heiko.hel...@horiba.com Cc: wpkg-users@lists.wpkg.org Subject: Re: [wpkg-users] Disable FBWF before installing software Am 14.11.2012 18:24, schrieb heiko.hel...@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. Top-posting: 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? ------------------------------------------------------------------------- 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 ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ Ce message et toutes les pièces jointes (ci-après le "message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur. --> Pensez à l'environnement avant d'imprimer ce message. This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. If you are not the intended addressee of this message, please delete it immediately and inform the sender. --> Please consider the environment before printing this email. ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ ------------------------------------------------------------------------- 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
