Hi Stefan,
On 22.07.2011 01:33, Rainer Meier wrote:
Since we now have extended host matching on nearly all nodes, I suggest the
following additional nodes to be supported:
1) depends ... for instance a package using RoboCopy depends on the RoboCopy
package on XP and below,
but for Vista and above RoboCopy is shipping with Windows already, so no
dependency needed.
2) download ... might be nice to have separate downloads, since it does not
make sense to download the 64-bit
package to a 32-bit machine
What does the group think?
Valid input. I will look into it. But not today, it's late and the risk to
introduce bugs is high ;)
Sorry for delay. I've just checked in an update which includes extended host
checks also for depends and download nodes. Moreover it also covers include and
chained packages.
Changes 2011-08-02, v1.2.1-RC7 by Rainer Meier <r.meier (at) wpkg.org>
NEW: Added extended host attribute matching support for the following package
notes:
<depends />
<include />
<chain />
<download />
As a result the following nodes cannow deal with extended host matching:
In hosts.xml:
<host name="..." proifile-id="..." os="..." ... />
<variable name="..." value="..." os="..." ... />
In profiles.xml:
<variable name="..." value="..." os="..." ... />
<package package-id="..." os="..." ... />
In packages.xml:
<variable name="..." value="..." os="..." ... />
<depends package-id="..." os="..." />
<include package-id="..." os="..." />
<chain package-id="..." os="..." />
<download url="..." target="..." os="..." />
<install cmd="..." os="..." />
<upgrade cmd="..." os="..." />
<downgrade cmd="..." os="..." />
<remove cmd="..." os="..." />
FIX: Fixed start notification text in English LCID specification in config.xml:
From: ...Plase safe all...
To: ... Please save all...
Thanks for Jeff Applegate for pointing this out.
FIX: Fixed long execution run times if many short-running external commands are
invoked. For example if many execute-style checks were invoked and each
check finished its task in less than 1s time, then WPKG would wait at
least 1 second for it to finish. Unfortunately WSH is not very advanced in
handling child processes but the algorithm has been changed in a way that
for the first 100ms of run time the child status is checked every 10ms.
For the next 1000ms the status is checked every 100ms. If the task is not
finished by then the task will be checked for termination once per second.
This allows short-running tasks to terminate quickly while preventing high
WPKG load for monitoring on long-lasting tasks.
Fixes bug 233. Thanks to Malte Starostik für suggestion.
<http://wpkg.svn.sourceforge.net/viewvc/wpkg/wpkg/stable/1.2/>
-------------------------------------------------------------------------
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
