Hi Steve, Steve Handy wrote: > Assuming this is true I need a way to eliminate the incrementing feature
Please see my answer to Adam regarding this. You don't need to increment the version to make sure a package is verified/re-installed. Just define appropriate checks and do _NOT_ use execute="once". If you use execute="once" it does exactly as the name implies, it executes this version just ONE SINGLE TIME. No further verification on the package is done during subsequent wpkg runs. Only if you increment the version on server side the package will be upgraded. So use execute="once" only (and really ONLY) in case you want to install a package, make sure it is once installed and then forget about it (no matter if somebody is going to uninstall it or not). Again, if you want to verify that a package is not removed by the user, then do NOT use execute="once" and define appropriate checks instead which make sure the software is actually installed. Also do not specify execute="always" as this will re-install the package on each synchronization. This could lead to quite high server load and annoy users if all software is re-installed on each boot-up :-) So just omit the execute="..." flag by default but make sure that you define appropriate checks. WARNING: If you do not use any execute="..." flag AND do not specify any checks, then the check will always return "false, not installed". Therefore the effect is similar (not exactly the same, but similar) to specifying execute="always". So let me repeat again: - do not specify any execute="..." flags if you don't have special requirements - Specify appropriate checks which return true in case the software is installed properly br, Rainer ------------------------------------------------------------------------- Do you use WPKG? Tell us how! >> http://wpkg.org/Testimonials _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users