-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rainer Meier wrote: > Hi Matt, Hi. Thanks for your informative reply. > It is common practice (well, I do it like this) to increment the package > revision AND update the check according to the conditions it should have > _after_ upgrade/install. This is exactly what I do currently. I'm just wondering if the logical check is necessary, or even detrimental. See my proposed client 3 below. > What will happen on your clients is depending on the client state. > > 1. Client with Firefox prior to 3.0.3 installed: <snip> > 2. Client without any Firefox installed: <snip> 3. Client with Firefox installed that doesn't have a Firefox entry in wpkg.xml (or no wpkg.xml): WPKG runs, sees it has Firefox 3.0 installed, which meets the logical check and adds Firefox to wpkg.xml at the current revision. The installed version is not the correct version, yet the revision is correct... Now we have to wait for the next update to be at the correct version. I think it's safer to remove the all but the check for the current version. <check type="uninstall" condition="exists" path="Mozilla Firefox (3.0.4)" /> This way, even if there's a mistake somewhere else, we're sure to get the current version of the package. > In general WPKG uses the checks defined for a package to verify that the > package is (still) installed properly. So in case WPKG installed Firefox > 3.0.4 and the user is manually remove it WPKG will detect this (by > failed check) and re-execute the install commands. This has not been my experience. Once a package is in wpkg.xml, WPKG seems to not use the checks anymore. Maybe because I'm using WPKG 0.9.10 still? - -- - - Matt Miller - Solutions for Progress 728 South Broad Street Philadelphia, PA 19146 215-701-6108 (v) 215-972-8109 (f) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJIxAKCg+4SLjWLD0RAiUWAJ9oXwTWP7vwqol3liO2mNjMzPWAtQCaAicN 4ypOTOsQVzhfCZMx9aZ29Vk= =SLWO -----END PGP SIGNATURE----- |