wpkg --force-configure-any ...

Submitted by Alexis Wilke on Wed, 12/05/2012 - 05:03
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

 

When installing a package, wpkg ensures that all packages that are dependencies of the package to be installed are fully configured and not just unpacked. If just unpacked, the installation fails by default.

The --force-configure-any option can be used to let the system configure all the packages that were unpacked and still need to be configured in order for the current installation to work as expected.

The use of this option is safe, although it is recommended that you check your installation and use an explicit --configure command instead if you want to be in full control of the status of your packages.

IMPORTANT NOTE

The --no-force-all, --refuse-all, --no-force-configure-any, --refuse-configure-any cancel this feature whatever the position of the different options on the command line.