Tomasz Chmielewski schrieb: (...)
> 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. Answering to myself: there is no obvious way to do it right now. You may do a couple of .xml files for each profile, or a batch file that makes some detection. It would be nice to have such a feature, for reference, I posted it here: http://bugs.wpkg.org/show_bug.cgi?id=69 Don't expect it to be implemented too fast though. -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- 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
