<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
Am 23.01.2012 20:40, schrieb <a class="moz-txt-link-abbreviated" href="mailto:ladiko@web.de:">ladiko@web.de:</a>
<blockquote
cite="mid:CA+LGGG-oYRTCUeYHFkby8ha98da2xXcrdsWdQDk72Mt8csbBYw@mail.gmail.com"
type="cite">
<p>Hello Marco,</p>
<p>this is not really related to my problem as the wpkg.xml is
updated at every run of wpkg. What i want is a single package
that runs only once a week or once a month while wpkg still can
run several times. So it seems like i have to place a file and
check its modification date as i mentioned in my first post.</p>
<p>Sorry for using TOFU post. The Android Gmail client doesn't
support editing in the quotation.</p>
<p>Regards Ronny</p>
<p>-- <br>
Sent from my mobile device.</p>
<div class="gmail_quote">Am 23.01.2012 11:22 schrieb "Marco
Gaiarin" <<a moz-do-not-send="true"
href="mailto:gaio@sv.lnf.it">gaio@sv.lnf.it</a>>:<br
type="attribution">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Mandi! Stefan Pendl<br>
In chel di` si favelave...<br>
<br>
> I see some problems with this approach:<br>
<br>
You're right, effectively after doing some test i realize that
i was<br>
wrong... simply because newer wpkg update the wpkg.xml file at
every<br>
step, not at the end.<br>
<br>
<br>
I've simply added, in wpkg client pre execution:<br>
<br>
if exist "%SystemRoot%\system32\wpkg.xml" (<br>
copy /y %SystemRoot%\system32\wpkg.xml
%SystemRoot%\system32\wpkg.old >nul<br>
)<br>
<br>
and now i check '%SystemRoot%\system32\wpkg.old'.<br>
<br>
This is not really a ''safe'' method, but can be useful in
some case.<br>
<br>
EG, i've prepared a recipe to install bacula file daemon
client, that i<br>
don't use extensively but only on some client; a second
recipe, if<br>
there's a server side .conf file, activate bacula and
configure it.<br>
<br>
With a check like that, i can add a client (or modify the
configuration<br>
file) and have the second recipe do the upgrade.<br>
Because normaly i do that not massively but on that pc, i can
check if<br>
works (really, i can do it manually, but using wpkg are very
cosy! ;).<br>
<br>
If i have some doubt, or i have to propagate some very
important<br>
update, i can upgrade revision and have a forced installation.<br>
<br>
<br>
Rougly: because i copy wpkg.xml to wpkg.old *before* wpkg.js
run, if<br>
some configuration file have a modification date newer then
wpkg.old,<br>
it is really a new file and have to be ''upgraded''.<br>
It is not true the opposite: but as stated, if really i need
to<br>
propagate some config options, i can update the revision.<br>
<br>
<br>
</blockquote>
</div>
</blockquote>
So it seems like there is no other wat than to check again a self
created file because wpkg.xml is changed every run which is too
often. Thank you for the hint regarding to "datemodifyolderthan".
Seems like it is not mentioned in the normal documentation.<br>
<br>
Kind regards Ronny :-)<br>
</body>
</html>