You are the current maintainer of a multi-purpose tool that has been around and used by a number of people for a long time.
I have used WPKG across about 10 primary schools (ages 5-11) where secure locked down networks are not required or needed. I believe that my suggestion of WPKG doing nothing if not instructed to do so is a reasonable suggestion. I don't expect that WPKG would be changed straight away just because I asked for it to be done. I do expect to be listened to and not told that I am doing things wrong :) You seem to have decided I am a bad person and that my suggestions/ideas are of very low value. I understand why you have modifed WPKG to work in the way it does to handle complex uninstall issues/bugs. That is good for you :) You do not seem able to understand that I do not have these issues but have much simpler ones. :) I am basically asking for WPKG to be slightly modified so that the /noforcedremove flag means that WPKG will not remove anything under any circumstances and not just the circumstances stated in the current config.xml documentation I believe I've know how to make this change but obviously I don't know if it would affect the stability of WPKG in other areas. I believe that my suggestion would be a very useful one during debugging/testing of hosts/profiles/packages and save time and effort during these phases and would have no negative effects on anyone choosing not to use the /noforcedremove flag. :) regards Simon -- View this message in context: http://www.nabble.com/package-is-run-one-more-time-after-removal-tp23834091p23864857.html Sent from the WPKG - Users mailing list archive at Nabble.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