sbotsford wrote:
Perhaps we need a 4th xml file for this.
After writing just a couple packages, I can see merit in being able to
define global environment variables for wpkg.
Example: suppose that my installation share point is
\\conan\installers\wpkg. I would much rather have $WPKG.
and later, as I accumulate bat files to run the two commands it takes to
install so many things, to be able to say
PATH=$WPKG/bat:$PATH
***
This may also be the right place to put things like
PACKAGES=$WPKG/xmlpacks/*.xml
PROFILES=$WPKG/xmlprof/*.xml
for people who want to have a bunch of little files instead of a few big
ones.
WPKG can use environmental variables.
See wpkg-start.bat.examples file that comes in the package:
:: You can also use variables...
set WPKGROOT=\\server\wpkg
set PACKAGES=%WPKGROOT%\packages
%WPKGROOT%\wpkg.js /synchronize /debug
:: ...and then, you can put into packages.xml something like:
<install cmd='%PACKAGES%\test\test.exe -silent' />
--
Tomasz Chmielewski
http://wpkg.org
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
wpkg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wpkg-users
