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
Hi Simon,
If you allow me to make one more proposal...
simplesi wrote:
The irritation is that I have removed a package from a profile but WPKG
thinks it is OK to run the package one more time :)
I would like to know if WPKG would behave as you expected if you comment out (or
delete) line 4547
Rainer Meier wrote:
Hi Simon,
If you allow me to make one more proposal...
Thank you very much for your proposal. :-)
I will try out your suggestion and get back to you as quickly as possible :)
regards
Simon
--
View this message in context:
Hi Simon,
simplesi wrote:
Another possibility, (But a lot more work!) would be to check to see if an
uninstall parameter exists - if no parameter exists then WPKG could ignore
the installPackage(serverPackage) line automatically - if an uninstall
parameter exists then the existing behaviour
Hello Simon,
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()
Rainer Meier wrote:
You did not answer yet if your packages define some checks.
I believe I published my package in my last post - I think you missed it :)
It does not have any checks
The only difference (and that's what is irritating you I think) is that
WPKG is
going to verify the
Hi Simon,
simplesi wrote:
I believe I published my package in my last post - I think you missed it :)
It does not have any checks
You're right. Even parts of your response I did not read because it was part of
the quoted text and therefore not obvious that you wrote it.
The only difference
Hi Simon,
simplesi wrote:
I am very sorry that you are unable to view WPKG as a tool that is used in
many different ways.
You seem to think that your way of package deployment is right and that
other ways are wrong.
This is not good.
I hope that in future, you will listen more to
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
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 sees the
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
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 will
12 matches
Mail list logo
