Michael J. Kidd wrote:
> Ok..
> From what I've read on the wpkg.org site ( specifically the
> packages.xml page ), it seems that as long as "execute='once'" is not
> declared, and there are not any <checks... /> then the package will be
> executed every time.
Indeed, that page fails to explain "execute='once'" ("always" was added
later as I remember).
> But, on another page on the wpkg.org site, it says to use
> "execute='always'" to accomplish this outcome.
What page is that? I'd like to update the docs.
> My personal experience goes along with the first exmple ( no 'once' and
> no 'checks' ). What is the way wpkg.js is "supposed" to handle this?
There is a difference between "once", "always", and no always/once + no
checks.
Here's a quick explanation (assuming there are no "check" conditions):
1) once - execute the package once, add it to wpkg.xml
2) always - execute the package always, add it to wpkg.xml
3) no once/always and no check condition
In this case, wpkg.js will execute all "install" commands, and in the
end will fail with "Could not install package_name". Failed checking
after installation.".
Nothing will get added to wpkg.xml, and you won't know if it was ever
executed, or not.
--
Tomasz Chmielewski
http://wpkg.org
_______________________________________________
wpkg-users mailing list
wpkg-users at lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
|
|