wpkg --no-force-file-info | --refuse-file-info ...

Submitted by Alexis Wilke on Wed, 02/13/2013 - 22:42
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 --no-force-file-info and --refuse-file-info options are used to make sure that the packager fails with an error if a file cannot be written, its permissions properly defined, or its ownership setup as expected.

This behavior is the default. Using one of these options allows you to make sure that the target remains safe.

The --force-file-info option can be used to prevent the failure of a call to chmod or chown from breaking the packager. This is safe whenever you are installing in your own environment (under your /home directory,) however, if you are installing a complete system, it can be a security issue. (i.e. if the wrong user has access to system files, it is definitively not secure.)

You may also want to have a look at the File-Owner and Group-Owner fields.