Rainer Meier wrote:
>
> However the issue you face with your packages might come from the fact
> that you
> did not specify appropriate checks for the packages. From your description
> I
> have to assume that you do not specify any checks. As a result the
> WPKG-internal
> isInstalled() check wi
Hi Simon,
simplesi wrote:
> In my package files, I NEVER have an uninstall script - I simply use WPKG to
> install and update software.
That's fine with WPKG. In this case during removal simply nothing will be
removed at all (no command executed).
However the issue you face with your packages mi
Rainer Meier wrote:
>
> Hi Simon,
> This might be because of the update-before-remove functionality...
>
OK - I've read some of the older posts about this functionality and I can
see it is a complicated subject :)
I realise this request might be shot down but hopefully you/we'll have a
nice d
Hi Simon,
simplesi wrote:
> When testing I removed a package from a profile but wpkg seemed to still run
> it the next time i ran my logon script (which does cscript
> %WPKGROOT%\wpkg.js /synchronize )
>
> It them doesn't do run it on subsequent runs.
>
> I'm assuming it looks in wpkg.xml and se
When testing I removed a package from a profile but wpkg seemed to still run
it the next time i ran my logon script (which does cscript
%WPKGROOT%\wpkg.js /synchronize )
It them doesn't do run it on subsequent runs.
I'm assuming it looks in wpkg.xml and sees the entry there and decides to
run it
