wpkg --force-distribution ...

Submitted by Alexis Wilke on Tue, 07/09/2013 - 02: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 --force-distribution option can be used to allow installation of a package with a distribution that is different from the distribution of the target system. By default, though, a target system is distribution agnostic and therefore this option is not at all necessary.

When you create a target with --create-admindir command you can specify a Distribution field to lock all the packages to that specific distribution. Trying to install packages from any other distribution fails with an error.

Say you installed a target with the Distribution field set to stable. Then only packages that were built for the stable Distribution are accepted by default. Other packages require the use of the --force-distribution to allow their installation on that target.