Am 23.01.2012 20:40, schrieb lad...@web.de:
Hello Marco,
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.
Sorry for using TOFU post. The Android Gmail client doesn't support
editing in the quotation.
Regards Ronny
--
Sent from my mobile device.
Am 23.01.2012 11:22 schrieb "Marco Gaiarin" <g...@sv.lnf.it
<mailto:g...@sv.lnf.it>>:
Mandi! Stefan Pendl
In chel di` si favelave...
> I see some problems with this approach:
You're right, effectively after doing some test i realize that i was
wrong... simply because newer wpkg update the wpkg.xml file at every
step, not at the end.
I've simply added, in wpkg client pre execution:
if exist "%SystemRoot%\system32\wpkg.xml" (
copy /y %SystemRoot%\system32\wpkg.xml
%SystemRoot%\system32\wpkg.old >nul
)
and now i check '%SystemRoot%\system32\wpkg.old'.
This is not really a ''safe'' method, but can be useful in some case.
EG, i've prepared a recipe to install bacula file daemon client,
that i
don't use extensively but only on some client; a second recipe, if
there's a server side .conf file, activate bacula and configure it.
With a check like that, i can add a client (or modify the
configuration
file) and have the second recipe do the upgrade.
Because normaly i do that not massively but on that pc, i can check if
works (really, i can do it manually, but using wpkg are very cosy! ;).
If i have some doubt, or i have to propagate some very important
update, i can upgrade revision and have a forced installation.
Rougly: because i copy wpkg.xml to wpkg.old *before* wpkg.js run, if
some configuration file have a modification date newer then wpkg.old,
it is really a new file and have to be ''upgraded''.
It is not true the opposite: but as stated, if really i need to
propagate some config options, i can update the revision.
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.
Kind regards Ronny :-)
-------------------------------------------------------------------------
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
