http://bugzilla.wpkg.org/show_bug.cgi?id=188 Rainer Meier <r.meier at wpkg.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |r.meier at wpkg.org --- Comment #3 from Rainer Meier <r.meier at wpkg.org> --- Maybe there is also a confusion how WPKG runs the commands. WPKG already executes all remove commands before applying any new installations or upgrades when a synchronization is run. If an upgrade requires to remove a previous version then command inheritance might be the answer. This discussion was already held on the mailing list. The outcome is summarized in Bug 184 and will be part of future WPKG releases. Command inheritance will allow you to inherit the remove commands as a complete group when performing an installation or upgrade (typically on upgrade). If you need to run a custom uninstall procedure there is nothing which prevents you to specify an upgrade command which performs the actual uninstall. No need to re-invent the wheel when it's already there. WPKG will execute all commands in order so feel free to add remove commands to the upgrade nodes too. At current stage for sure you will probably have to copy some "remove" instructions and make them re-appear as upgrade instructions but as I said in future versions you will be able to inherit a complete set of commands. -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |