wpkg --force-conflicts ...

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

 

Different packages may not be compatible with each others. In that case, one package marks the other as being in conflict. This prevents the installation administrator from simultaneously installing two packages that are in conflict since wpkg can detect the problem on its own.

There are two main reasons for marking two distinct packages as being in conflict:

1) Both offer the same set of files (such as a dynamic link library of the exact same name);

2) Both offer the same functionality (i.e. low level sub-system to send emails to other computers, web servers, etc.)

Whatever the reason, it is important to mark modules as conflicting to ensure that target systems remain as stable as possible.

The --force-conflicts option can be used to ignore conflict errors and still install a set of packages together even if by default they should not be installed at the same time on the target machine.

The use of this command line option is not recommended.

IMPORTANT NOTE

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