wpkg --no-force-all | --refuse-all ...

Submitted by Alexis Wilke on Wed, 12/05/2012 - 06:47
All Force Options
--force-all --no-force-all
--refuse-all
--force-architecture --no-force-architecture
--refuse-architecture
--force-breaks --no-force-breaks
--refuse-breaks
--force-configure-any --no-force-configure-any
--refuse-configure-any
--force-conflicts --no-force-conflicts
--refuse-conflicts
--force-depends --no-force-depends
--refuse-depends
--force-depends-version --no-force-depends-version
--refuse-depends-version
--force-distribution --no-force-distribution
--refuse-distribution
--force-downgrade --no-force-downgrade
--refuse-downgrade
--force-file-info --no-force-file-info
--refuse-file-info
--force-hold --no-force-hold
--refuse-force-hold
--force-overwrite --no-force-overwrite
--refuse-overwrite
--force-overwrite-dir --no-force-overwrite-dir
--refuse-overwrite-dir
--force-remove-essential --no-force-remove-essential
--refuse-remove-essential
--force-rollback --no-force-rollback
--refuse-rollback
--force-upgrade-any-version --no-force-upgrade-any-version
--refuse-upgrade-any-version
--force-vendor --no-force-vendor
--refuse-vendor

 

The --no-force-all option prevents all the --force-... options. This is true no matter what. That is, the option can appear first or last on the command line and it will always have exactly the same effect: prevent ALL --force-... options. The reason for this behavior is because this is the default and it is considered safe.

This option is not exactly the opposite of the --force-all since the --force-all does not force the --force-overwrite-dir option whereas the --no-force-all does prevent it.

This option is particularly useful on a command line where outside users may be able to add other options, including the --force-... options, and the software would not otherwise be sure that the packager is still being used in a safe manner.

--refuse-all is an exact equivalent.