wpkg --remove | -r

Short Hand

wpkg -r

Options Comments
--admindir Define the administration directory, where the database of the installed packages resides.
--debug Define a set of flags of things to print out for debug purposes.
--dry-run Run all validations then exit.
--force-all Ignore all problems that can be bypassed.
--force-depends Accept installing packages with missing dependencies.
--force-hold Remove package even if marked as being on hold.
--force-remove-essential Allow wpkg to delete essential packages
--instdir Define the installation directory, where the data files are installed on the target.
--no-act Run all validations then exit.
--no-force-all Prevent any --force-... command line option from being used.
--no-force-depends Prevent packages with missing dependencies from being installed.
--no-force-hold Prevent packages that are on hold from being removed.
--no-force-remove-essential Prevent the removal of essential packages, this is the default.
--quiet Request for minimal output. For the --verify function this is the default behavior.
--recursive Recursively scan the --repository directories or remove all dependencies automatically.
--refuse-all Prevent all problems from ever being bypassed.
--refuse-depends Prevent packages with missing dependencies from being installed.
--refuse-hold Prevent packages that are on hold from being removed.
--refuse-remove-essential Prevent the removal of essential packages, this is the default.
--root Define the installation root path.
--simulate Run all validations then exit.
--tracking-journal Specify the filename of the journal where commands that can be used to rollback the system are saved.
--verbose Display log information of level INFO.

 

The --remove command is used to remove a package from a target machine. The --remove command works against packages that were not properly installed so as to allow you to repair an installation target. Yet, only packages that were previously installed and not yet removed can be removed.

The --remove command deletes all the files except the configuration files that the packager installed with the --install command. Dynamically created files are expected to be deleted whenever the package post-remove script is executed.

If you are removing a server, the prerm script should automatically stop the server before removal. Note that MS-Windows executables are locked while the corresponding software is running. In other words, such executables cannot be removed as expected. For this reason, prerm scripts should be used to test whether any one of the executables are still running and if so and your script is not capable to stop them, prevent the removal completely. wpkg does not check, however, if it fails removing a file, it will abort the removal.

To remove the configuration files, you can either use the --deconfigure or the --purge commands at a later time.

To automatically remove packages that are not necessary anymore, the --autoremove command can be used. This command removes packages that were automatically installed to satisfy a dependency (implicitly installed packages.)

 
Syndicate content