Falko Trojahn <nospam...@smi-softmark.de> writes:
[...] > Well, up to now, all command line parameters have had their counterpart > in config.xml, so no need to specify command line parameters. No, the /host, /query, /install, /remove, /upgrade does not have config.xml couterpart, they have no meaning here. > If you really need 'em, you can put a "cmdlineparams.txt" in a test dir > and I'll have a look at "testone.cmd", how to read this file (if it > exists) into a variable. Maybe a call on a cmdlineparams.cmd to define a variable ? - Use SETLOCAL/ENDLOCAL to avoid environnement pollution - a cmdlineparams.cmd define a variable, like %WPKG_CMD_PARAMS% - in testone.cmd: * IF EXIST "%1\%2\cmdlineparams.cmd" CALL "%1\%2\cmdlineparams.cmd" * cscript [...] %WPKG_CMD_PARAMS% > But, this way it would be possible to break "testone.cmd" ... so, let's > see how to achieve this. Regards. -- Daniel Dehennin RAIP de l'Orne
pgpXnfB1NPyp8.pgp
Description: PGP signature
------------------------------------------------------------------------- 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
