I'm forwarding this email, as the author has problems getting it to the list:
We use .msi installers to deploy all our internal/production software. We have a need to run all our .msi's in several different environments with a parameter passed in on the command line that represents the type of environment we are installing to. Like this: Msiexec /i myinstaller.msi /qb TARGET_ENVIRONMENT=QA Msiexec /i myinstaller.msi /qb TARGET_ENVIRONMENT=DEV Msiexec /i myinstaller.msi /qb TARGET_ENVIRONMENT=PRODUCTION My thought was to use different profiles for each type of environment and associate them with hosts. We have hundreds of installers and use a small batch command to run through them in groups, but I still need a way to pass in the TARGET_ENVIRONMENT setting each time. Is there a way to refer to a profile name in other sections of WPKG? I'd like to be able to do something like this: Msiexec /i myinstaller.msi /qb TARGET_ENVIRONMENT=$(current.profile) ... so the command can be as generic as possible. Thanks! Awesome program, by the way! ---------- Matthew Janulewicz SCM Engineer Green Dot Corporation [EMAIL PROTECTED] (626) 775-3857 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wpkg-users
