Dominique Dumont
and 1 contributors


Config::Model::models::Dpkg - Configuration class Dpkg


Configuration classes used by Config::Model

Model of Debian source package files (e.g debian/control, debian/copyright...)



This element contains a set of parameters to tune the behavior of this dpkg editor. You can for instance specify e-mail replacements. These parameters are stored in ~/.dpkg-meta.yml or ~/.local/share/.dpkg-meta.yml. These parameters can be applied to all Debian packages you maintain in this unix account.Optional. Type node of class Dpkg::Meta .


Package control file. Specifies the most vital (and version-independent) information about the source package and about the binary packages it creates.Optional. Type node of class Dpkg::Control .

rules - package build rules

debian/rules is a makefile containing all intructions required to build a debian package.Optional. Type string.

copyright and license information of all files contained in this package. Optional. Type node of class Dpkg::Copyright .


Optional. Type node of class Dpkg::Source .

clean - list of files to clean

list of files to remove when dh_clean is run. Files names can include wild cards. For instance:


Optional. Type list of uniline.


Optional. Type hash of node of class Dpkg::Patch .


compat file defines the debhelper compatibility level. Optional. Type integer. default: '9'.

dirs - Extra directories

This file specifies any directories which we need but which are not created by the normal installation procedure (make install DESTDIR=... invoked by dh_auto_install). This generally means there is a problem with the Makefile.

Files listed in an install file don't need their directories created first.

It is best to try to run the installation first and only use this if you run into trouble. There is no preceding slash on the directory names listed in the dirs file. Optional. Type list of uniline.


This file specifies the file names of documentation files we can have dh_installdocs(1) install into the temporary directory for us.

By default, it will include all existing files in the top-level source directory that are called BUGS, README*, TODO etc. Optional. Type list of uniline.



Dominique Dumont


2010,2011 Dominique Dumont