These are identified options in the DPM configuration file. The DPM configuration file is intended to be places at /etc/dpm/config.
force_signature_validation
Enables the signature validation requirement for a package to install. Can still be overridden with an optional switch.
force_integrity_validation
Enables the package integrity validation requirement for a package to install. Can still be overridden with an optional switch.
signature_method
Defaults to SHA-256. Other options will be available provided by the library that supplies supported cryptographic methods to use.
target_rootfs
Defaults to '/'. This tells DPM when working with package contents the root directory of where to install those contents. So, for instance, if you had a custom solution you were building, like a chroot, container directory tree, or a sysroot, or some other use, you could set this to the top-level directory of where that would be so that you could populate that directory as opposed to the root filesystem of the linux distribution.
This can also be supplied as a commandline option when installing a package. If supplied as a commandline option, the supplied commandline option will take priority over this value.
accepted_architectures
A comma delimited list of acceptable architectures.
For example, on a multilib x86_64 system, you’d probably want:
accepted_architectures = i686, noarch, x86_64Or perhaps for an aarch64 system, you’d set this to noarch, x86_64.