wpkg --configure

Submitted by Alexis Wilke on Thu, 12/13/2012 - 11:15
Options Comments
--admindir Define the administration directory, where the database of the installed packages resides.
--build [Only with --install] Using this command along the --install command is the same as doing --build-and-install.
--debug Define a set of flags of things to print out for debug purposes.
--dry-run Run all validations then exit.
--force-all Ignore all problems that can be bypassed.
--force-architecture Ignore architecture mismatch errors.
--force-breaks Allow the installation of packages that break others.
--force-configure-any Automatically configure packages that were only unpackaged earlier.
--force-conflicts Accept packages even if they are in conflict with others.
--force-depends Accept installing packages with missing dependencies.
--force-depends-version Accept installing packages with dependencies having incompatible versions.
--force-downgrade Allow a package to be dowgraded.
--force-hold Force an upgrade to occur even if one of the explicit packages is currently on hold.
--force-overwrite Allow a package to overwrite another's file(s).
--force-overwrite-dir Allow the system to overwrite directories with files and vice versa.
--instdir Define the installation directory, where the data files are installed on the target.
--interactive Allow wpkg to interactively request a username and password when necessary to access a remote drive.
--no-act Run all validations then exit.
--no-force-all Prevent any --force-... command line option from being used.
--no-force-architecture Prevent package with an incompatible architectures from being installed.
--no-force-breaks Prevent the installation of package if marked as breaking each others.
--no-force-configure-any Do no automatically configure packaages. If a dependency is an unpacked package, then the verification fails.
--no-force-conflicts Prevent incompatible packages from being installed along each others.
--no-force-depends Prevent packages with missing dependencies from being installed.
--no-force-depends-version Prevent installing packages if dependency versions are not compatible.
--no-force-downgrade Prevent a package from being downgraded (a smaller version cannot be installed.)
--no-force-hold Prevent upgrading a package if it is currently on hold.
--no-force-overwrite Forbid any package from overwriting any file while being installed.
--no-force-overwrite-dir Prevent the overwrite feature on directory.
--quiet Request for minimal output. For the --verify function this is the default behavior.
--recursive Recursively scan the --repository directories or remove all dependencies automatically.
--refuse-all Prevent all problems from ever being bypassed.
--refuse-architecture Prevent package with an incompatible architecture from being installed.
--refuse-breaks Prevent the installation of package if marked as breaking each others.
--refuse-configure-any Do no automatically configure packaages. If a dependency is an unpacked package, then the verification fails.
--refuse-conflicts Prevent incompatible packages from being installed along each others.
--refuse-depends Prevent packages with missing dependencies from being installed.
--refuse-depends-version Prevent installing packages if dependency versions are not compatible.
--refuse-downgrade Prevent a package from being downgraded (a smaller version cannot be installed.)
--refuse-hold Prevent an upgrade of a package that is on hold.
--refuse-overwrite Forbid any package from overwriting any file while being installed.
--refuse-overwrite-dir Prevent the overwrite feature on directory.
--repository List of directories used as repositories for package dependencies.
--root Define the installation root path.
--simulate Run all validations then exit.
--skip-same-version Do not reinstall a package if that same version is already installed.
--tracking-journal Specify the filename for the tracking journal that can be used to rollback changes made by installation commands.
--verify-fields Ensure fields validity before processing.
--verbose Display log information of level INFO.

 

The --configure command is used to configure a package that was previously unpacked with the --unpack command.

The installation validation process is run before the configuration takes place. If the package breaks another then the configuration cannot happen. The validation ensures that only unpacked packages were selected for configuration.

Since only already unpacked packages can be configured with this command, it means the command only accept names of unpacked packages (in other words, no slashes or underscores in the name.)

The --configure command runs the post installation scripts (postinst) with the keyword configure and the version of the package1.

Note that if the configuration script fails, an error is printed, but nothing else happen. The system does not try to fix that package installation by running another script. In that case the package remains in the Half-Configured state.

For more detailed information, check out the Configuring chapter of the --install command. Especially, you may be interested in the naming convention of configuration files recognized by wpkg.

The opposite of the --configure command is --deconfigure, although the configuration files are renamed .wpkg-user instead of .wpkg-new as expected by default by the --configure command (the --unpack process generates configuration files with the .wpkg-new extension.)

 
  • 1. Note that dpkg does not always pass the package version along! This is different in wpkg.