Hi Chris, On 23.11.2011 22:09, Chris Mortimer wrote: > Thanks for your reply. All makes sense apart from > > 'The exception being > upgrades to packages scheduled for removal and then maybe (?) upgrades to their dependencies.' > > sorry, not sure I follow this bit. Do you mean that if a package has been removed from profiles.xml and that package has also been edited to upgrade it, the upgrade will happen first, then it will be removed? Yes, exactly this is the case. WPKG has a feature I call "upgrade-before-remove". It was introduced to help package admins to fix broken packages easily. So if you made a mistake, let's say your flash10 package installed to clients does not correctly uninstall (maybe you just forgot to specify correct remove commands) then you don't have to worry. Just fix up your flash10 package on server side, bump the revision number and remove it from the profile. WPKG will then first upgrade flash10 to the latest available revision to assure that the latest/fixed package is applied to the system. Then WPKG performs the remove. WPKG will still first perform all removes before performing any installation. But as you see in some exceptional cases (client runs outdated version of a package to be removed) an upgrade will take place right before the remove. Hope this makes any sense to you ;) br, Rainer |