wpkg --force-depends ...

Before installing a package, the installation process validates the dependencies defined in the packages being installed. All Depends dependencies must be satisfied one way or the other:

  • The dependency may already be installed with the correct version,
  • The dependency may be specified on the installation command line (in any order,)
  • The dependency may be defined in a repository directory,
  • The --force-depends option was specified and none of the --no-force-depends or equivalent options were specified.

If all those checks fail, then the installation fails.

Note that the dependency tests include a package name, an architecture1, and a version check.

The --force-depends option allows you to force the installer to proceed even when one or more dependencies are missing.


It is important to note that the --force-depends option allows the installation of a package even when one or more of its dependencies are missing. However, note that even if you offer a repository directory and some of those dependencies could be satisfied, none will. In other words, when the --force-depends option is used, absolutely no implicit packages get installed.

The use of this option is not recommended.


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

  • 1. The architecture is implicit as we use the test of the target system architecture which can be ignored using the --force-architecture option. This works because at this point the target system cannot support more than one architecture with wpkg.
Syndicate content