Difference between revisions of "WPKG flags"
(fix a few nits) |
|||
| Line 31: | Line 31: | ||
'''/force''' - Uses force when performing actions (does not honour wpkg.xml). Handy when you're not sure if your system is "up to date" with the state described in hosts.xml, packages.xml and profiles.xml (i.e., when someone was adding / removing software by other means than WPKG). It will "scan" your system for all possible packages from packages.xml, and then, install and/or uninstall packages, according to profiles.xml / packages.xml / hosts.xml for a given host. | '''/force''' - Uses force when performing actions (does not honour wpkg.xml). Handy when you're not sure if your system is "up to date" with the state described in hosts.xml, packages.xml and profiles.xml (i.e., when someone was adding / removing software by other means than WPKG). It will "scan" your system for all possible packages from packages.xml, and then, install and/or uninstall packages, according to profiles.xml / packages.xml / hosts.xml for a given host. | ||
| − | '''/forceinstall''' - Forces installation over existing packages. The "install" command will be run, even if "check" conditions are met. This can be useful to "repair" packages etc. | + | '''/forceinstall''' - Forces installation over existing packages. The "install" command will be run, even if "check" conditions are met. This can be useful to "repair" packages etc. Don't use it, unless you really know what you're doing - it will start all your install commands for all packages. A better way is to increase a package revision for a single package (the one you know is broken), and make an "upgrade" of that single package. |
'''/norunningstate''' - Do not export the running state to the registry (HKLM\Software\WPKG\running set to true when WPKG is running, set to false when it finishes). | '''/norunningstate''' - Do not export the running state to the registry (HKLM\Software\WPKG\running set to true when WPKG is running, set to false when it finishes). | ||
Revision as of 16:31, 26 November 2007
WPKG flags (for WPKG-0.9.10):
/profile:<profile> - Forces the name of the current profile. If not specified, the profile is looked up using hosts.xml.
/base:<path> - Sets the local or remote path to find the settings files.
/query:<option> - Displays a list of packages matching the specified criteria. Valid options are:
a - all packages
i - packages that are currently installed on the system
x - packages that are not currently installed on the system
u - packages that can be upgraded
/show:<package> - Displays a summary of the specified package, including its state.
/install:<package> - Installs the specified package on the system.
/remove:<package> - Removes the specified package from the system.
/upgrade:<package> - Upgrades the already installed package on the system.
/synchronize - Synchronizes the current program state with the suggested program state of the specified profile. This is the action that should be called at system boot time for this program to be useful.
/quiet - Uses the event log to record all error/status output. Use this when running unattended.
/nonotify - Logged on users are not notified about impending updates.
/noreboot - System does not reboot regardless of need.
/rebootcmd:<option> - Use the specified boot command, either with full path or relative to location of wpkg.js. Specifying "special" as option uses tools\psshutdown.exe from www.sysinternals.com - if it exists - and a notification loop.
/force - Uses force when performing actions (does not honour wpkg.xml). Handy when you're not sure if your system is "up to date" with the state described in hosts.xml, packages.xml and profiles.xml (i.e., when someone was adding / removing software by other means than WPKG). It will "scan" your system for all possible packages from packages.xml, and then, install and/or uninstall packages, according to profiles.xml / packages.xml / hosts.xml for a given host.
/forceinstall - Forces installation over existing packages. The "install" command will be run, even if "check" conditions are met. This can be useful to "repair" packages etc. Don't use it, unless you really know what you're doing - it will start all your install commands for all packages. A better way is to increase a package revision for a single package (the one you know is broken), and make an "upgrade" of that single package.
/norunningstate - Do not export the running state to the registry (HKLM\Software\WPKG\running set to true when WPKG is running, set to false when it finishes).
/quitonerror - Quits execution if installation of any package was unsuccessful (default: install next package and show the error summary).
/debug or /verbose - Prints some debugging info. Prints everything WPKG does, useful for package installation debugging (and for new users which need to understand how WPKG works).
/dryrun - "Simulates" package installing, without installing anything. Does not execute any action. Assumes /debug on.
/help - Shows these flags with brief description message.