Rechercher une page de manuel

Chercher une autre page de manuel:


Langue: en

Version: 2008-11-22 (ubuntu - 07/07/09)

Section: 1 (Commandes utilisateur)


dh-make-perl - Create debian source packages from perl modules


dh-make-perl [SOURCE_DIR | --cpan MODULE]

dh-make-perl --refresh

You can modify dh-make-perl's behaviour with some switches:

Uses the argument to --desc as short description for the package.
--arch any | all
This switches between arch-dependent and arch-independet packages. If --arch isn't used, dh-make-perl uses a relatively good-working algorithms to decide this alone.
--version VERSION
Specifies the version of the resulting package.
--email | -e EMAIL
Manually specify the Maintainer email address to use in debian/control and in debian/changelog.
--packagename | -p PACKAGENAME
Manually specify the Package Name, useful when the module has dashes in its name.
--closes ITPBUG
Manually specify the ITP bug number that this package closes. If not given, dh-make-perl will try to connect to to fetch the appropriate bug number, using WWW::Mechanize.
--depends DEPENDS
Manually specify the string to be used for the module's dependencies. This should be used when building modules where dh-make-perl cannot guess the Perl dependencies (such as modules built using Module::Install), or when the Perl code depends on non-Perl binaries or libraries. Usually, dh-make-perl will figure out the dependencies by itself. If you need to pass dh-make-perl dependency information, you must do it using the debian package format. i.e.

dh-make-perl --depends libtest-more-perl

--bdepends BUILD-DEPENDS
Manually specify the string to be used for the module's build-dependencies (that is, the packages and their versions that have to be installed in order to successfully build the package). Keep in mind that packages generated by dh-make-perl require debhelper to be specified as a build dependency. Same note as for --depends applies here - Use only when needed.
Manually specify the string to be used for the module's build-dependencies for architecture-independent builds. Same notes as those for the --depends and --bdepends options apply here.

Note that for --depends, --bdepends and --bdependsi you can also specify that the field should not appear in debian/rules (if you really mean it, of course ;-) ) by giving it an empty string as an argument.

Useful when preparing a package for the Debian Perl Group <>.

Sets "Maintainer", "Uploaders", "Vcs-Svn" and "Vcs-Browser" fields in debian/control accordingly, and sets packaging-related licensing to GPLv2.

--cpan-mirror MIRROR
Specifies a CPAN site to use as mirror.
--exclude | -i [REGEX]
This allows you to specify a PCRE to exclude some files from the search for docs and stuff like that. If no argument is given (but the switch is specified - not specifying the switch will include everything), it defaults to exclude CVS and .svn directories.
Builds the package after setting it up.

NB: This builds only a binary package (by calling ``fakeroot debian/rules binary'') and does not sign the package. It is meant for a quick local install of a package, not for creating a package ready for submission to the Debian archive.

Installs the freshly built package. Specifying --install implies --build - The package will not be installed unless it was built (obviously ;-) )
Does not run the automatic testing of the module as part of the build script. This is mostly useful when packaging buggy or incomplete software.
Explicitly gives a comma-separated list of packages to consider ``base'' packages (i.e. packages that should always be available in Debian systems). This option defaults to "perl,perl-base,perl-modules" - It is used to check for module dependencies. If a needed module is in the "basepkgs", it won't be mentioned in the "depends:" field of "debian/control".

If this option is specified, the above mentioned default packages will not be included (but will be mentioned as explicit dependencies in the resulting package). You can, of course, mention your own modules and explicitly specify the default values.

Note that this option should be used sparsingly and with care, as it might lead to packages not being rebuildable because of unfulfilled dependencies.

Fail if a dependency perl package was not found (dependency tracking requires the apt-file package installed and updated)
Allows building core Perl modules. By default, dh-make-perl will not allow building a module that is shipped as part of the standard Perl library; by specifying this option, dh-make-perl will build them anyway.

Note that, although it is not probable, this might break unrelated items in your system - If a newer version of a core module breaks the API, all kinds of daemons might get upset ;-)

Refresh mode.

Instead of creating new debian/ directory, --refresh makes dh-make-perl to re-create only debian/rules according to the current templates.

This is useful when debian/rules was created using older templates and doesn't contain much customisations. As always, you're strongly encouraged to verify if debian/rules looks sane.

--dh ver
Set desired debhelper version. If "ver" is 7, generated debian/rules is minimalistic, using the auto-mode of debhelper. Also, any additional documentation and examples are listed in additional files under debian/, instead of being listed in debian/rules


dh-make-perl will create the files required to build a debian source package out of a perl package. This works for most simple packages and is also useful for getting started with packaging perl modules.

You can specify a module name with the --cpan switch and dh-make-perl will download the module for you from a CPAN mirror, or you can specify the directory with the already unpacked sources. If neither --cpan nor a directory is given as argument, dh-make-perl tries to create a perl package from the data in .

There is an override mechanism in place to handle most of the little changes that may be needed for some modules (this hasn't been tested much, though, and the override database needs to be filled in).

You can build and install the debian package using the --build and --install command line switches.

Using this program is no excuse for not reading the debian developer documentation, including the Debian policy, the perl policy, the packaging manual and so on.


The following directories will be searched to find additional files required by dh-make-perl:

File that overrides information retreived (or guessed) about the package. All the files in the library directories are loaded: entries in the home take precedence. See the distributed overrides file for usage information.


A debian/rules makefile for modules that use ExtUtils::MakeMaker, but don't have C/XS code.


A debian/rules makefile for modules that use ExtUtils::MakerMaker and C/XS code.


A debian/rules makefile for modules that use Module::Build, but don't have C/XS code.


A debian/rules makefile for modules that use Module::Build and C/XS code.


HOME - get user's home directory

DEBFULLNAME - get the real name of the maintainer

LOGNAME or USER - get the username

DEBEMAIL or EMAIL - get the email address of the user


Several, let me know when you find them.


Paolo Molaro <> (MIA)

Maintained for a time by Ivan Kohler <>.

Maintained for a time by Marc Brockschmdit <>.

Now maintained by Gunnar Wolf <>, and team-maintained by the Debian pkg-perl team,

Patches from:

Adam Sjoegren <>
Adrian Phillips <>
Amos Shapira <>
Christian Kurz <>
Damyan Ivanov <>
David Paleino <>
David Pashley <>
Edward Betts <>
Fermin Galan <>
Geoff Richards <>
Gergely Nagy <>
gregor herrmann <>
Hilko Bengen <>
Kees Cook <>
Jesper Krogh <>
Johnny Morano <>
Juerd <>
Marc Chantreux (mail withheld)
Matt Hope <>
Noel Maddy <>
Oliver Gorwits <>
Peter Moerch <>
Stephen Oberholtzer <>
Ton Nijkes <>

... And others who, sadly, we have forgot to add :-/

La science sans épistémologie -à supposer qu'elle soit pensable- est
primitive et brouillonne. Néanmoins, dès que l'épistémologue, qui
cherche un système clair, en a trouvé un, il est enclin à interpréter le
contenu de la science à travers son système et à rejeter ce qui n'y
rentre pas. Le scientifique, par contre, ne peut pas se permettre de
pousser loin son désir de systématicité épistémologique. [...] Il doit
donc paraître aux yeux de l'épistémologue comme un opportuniste sans
-+- Albert Einstein -+-