CDBS Documentation

Suppose you want custom rules for the source package foo, creating foo (arch-dep) and foo-data (arch-indep), you simply need to add some lines to debian/rules.

To add pre-configure actions:

makebuilddir/foo::
   ln -s plop plop2
						

To add post-configure actions:

configure/foo::
   sed -ri 's/PLOP/PLIP/' Makefile

configure/foo-data::
   touch src/z.xml
						

/!\ in this case we are talking about package configuration and NOT about a configure script made with autotools.

To add post-build actions:

build/foo::
   /bin/bash debian/scripts/toto.sh

build/foo-data::
   $(MAKE) helpfiles
						

To add post-install actions:

install/foo::
   cp debian/tmp/myfoocmd debian/foo/foocmd
   find debian/foo/ -name "CVS" -depth -exec rm -rf {} \;

install/foo-data::
   cp data/*.png debian/foo-data/usr/share/foo-data/images/
   dh_stuff -m ipot -f plop.bz3 debian/foo-data/libexec/
						

To add post deb preparation actions:

binary/foo::
   strip --remove-section=.comment --remove-section=.note --strip-unneeded \
      debian/foo/usr/lib/foo/totoz.so
						

To add pre-clean actions:

cleanbuilddir/foo::
   rm -f debian/fooman.1
						

First, patching sources directly is really BAD™, so you need a way to apply patches without touching any files. These rules, inspired by the Dpatch system, are quite similar and powerful. All you need is diff/patch knowledge, CDBS is doing the rest.

That's quite hard, so please listen carefully and prepare for examination.

First, add this line to your debian/rules:

include /usr/share/cdbs/1/rules/simple-patchsys.mk
						

And then use it !

Create the directory debian/patches and put your patches in it. Files should be named so as to reflect in which order they have to be applied, and must finish with the .patch or .diff suffix. The class would take care of patching before configure and unpatch after clean. It is possible to use patch level 0 to 3, and CDBS would try them and use the right level automatically. The system can handle compressed patch with additional .gz or .bz2 suffix and uu-encoded patches with additional .uu suffix.

You can customize the directories where patches are searched, and the suffix like this: (defaults are: .diff .diff.gz .diff.bz2 .diff.uu .patch .patch.gz .patch.bz2 .patch.uu)

DEB_PATCHDIRS := debian/mypatches
DEB_PATCH_SUFFIX := .plop
						

In case of errors when applying, for example debian/patches/01_hurd_ftbfs_pathmax.patch, you can read the log for this patch in debian/patches/01_hurd_ftbfs_pathmax.patch.level-0.log ('0' because a level 0 patch).

To use Dpatch as an alternative to the CDBS included patch system, just add his line to your debian/rules:

include /usr/share/cdbs/1/rules/dpatch.mk
# needed to use the dpatch tools (like dpatch-edit-patch)
include /usr/share/dpatch/dpatch.make
						

Now you can use Dpatch as usual and CDBS would call it automatically.

To use Quilt as an alternative to the CDBS included patch system, just add his line to your debian/rules:

include /usr/share/cdbs/1/rules/patchsys-quilt.mk
						

Now you can use Quilt as usual and CDBS would call it automatically.

Yes, CDBS is doing almost everything for you :).

Just add this line to the beginning of your debian/rules file:

include /usr/share/cdbs/1/rules/debhelper.mk
					

In case of a missing compat information, CDBS would create a debian/compat file with compatibility level 7. If you are using an obsolete DH_COMPAT variable in your debian/rules, you should get rid of it. In this case, or in case you would like CDBS not to create a debian/compat file, you can disable this feature by setting DEB_DH_COMPAT_DISABLE to a non-void value.

Extra variables you can use in debian/rules with these rules:

Extra targets can be used in debian/rules with these rules (called in this order):

For example, to add post install preparation (after debhelper work):

binary-install/foo::
   chmod a+x debian/foo/usr/bin/pouet
							

These rules handles the following debhelper commands for each binary package automatically (with the parameters you can use to customize their behavior):

Other debhelper commands can be handled in specific classes or may be called in custom rules.

To specify a tight dependency on a package containing shared libraries:

DEB_DH_MAKESHLIBS_ARGS_libfoo := -V"libfoo (>= 0.1.2-3)"
DEB_SHLIBDEPS_LIBRARY_arkrpg := libfoo
DEB_SHLIBDEPS_INCLUDE_arkrpg := debian/libfoo/usr/lib/
						

To install a changelog file with an uncommon name as ProjectChanges.txt.gz:

DEB_INSTALL_CHANGELOGS_ALL := ProjectChanges.txt
						

To avoid compressing files with i.py extension:

DEB_COMPRESS_EXCLUDE := .py
						

To register a debug library package libfoo-dbg for libfoo (which needs unstripped .so) in compat mode 4:

DEB_DH_STRIP_ARGS := --dbg-package=libfoo
						

Starting from compat mode 5, CDBS automatically detect -dbg packages and pass the needed arguments to dh_strip; DEB_DH_STRIP_ARGS can still be useful to pass additional parameters like excluded items (--exclude=item).

Perl-specific debhelper options (dh_perl call is always performed):

# Add a space-separated list of paths to search for perl modules
DEB_PERL_INCLUDE := /usr/lib/perl-z
# Like the above, but for the 'libperl-stuff' package
DEB_PERL_INCLUDE_libperl-stuff := /usr/lib/perl-plop

# Overrides options passed to dh_perl
DEB_DH_PERL_ARGS := -d
						

To avoid loosing temporary generated files in dh_clean processing (rarely useful):

# files containing these pattern would not be deleted
# (beware CDBS changelog has a typo while highlighting new DEB_CLEAN_EXCLUDE*S* feature)
DEB_CLEAN_EXCLUDE := precious keep
						

This class is for the guys who only have a Makefile (no autotools available) to build the program. You only need to have four rules in the Makefile:

To be honest, the install rules is not a must-have, but it always helps a lot when you've got it.

include /usr/share/cdbs/1/class/makefile.mk
							

DEB_MAKE_CLEAN_TARGET    := mrproper
# if you detect authors's loss of sanity, tell CDBS not to try running the nonexistent clean rule, and do the job yourself in debian/rules
DEB_MAKE_CLEAN_TARGET    :=
DEB_MAKE_BUILD_TARGET    := myprog 
DEB_MAKE_INSTALL_TARGET  := install DESTDIR=$(CURDIR)/debian/tmp/
# no check for this software
DEB_MAKE_CHECK_TARGET :=

# allow changing the makefile filename in case of emergency exotic practices
DEB_MAKE_MAKEFILE        := MaKeFiLe
# example when changing environment variables is necessary:
DEB_MAKE_ENVVARS    := CFLAGS="-fomit-frame-pointer"
							

# needs to be declared before including makefile.mk
DEB_MAKE_FLAVORS = full nox light
DEB_BUILDDIR = build
							

$(cdbs_make_clean_nonstamps)::
	$(if $(cdbs_make_flavors),rm -f extra-stuff-$(cdbs_make_curflavor))

$(cdbs_make_install_stamps)::
	$(if $(cdbs_make_flavors),dostuff --with=$(cdbs_make_curflavor))
							

This class is able to use configure scripts and makefiles generated with autotools (and possibly libtool). All rules are called automatically and clean rules to remove generated files during build are also added. This class in fact improves the makefile class to support autotools features and provide good defaults.

include /usr/share/cdbs/1/class/autotools.mk
							

DEB_CONFIGURE_EXTRA_FLAGS := --with-ipv6 --with-foo
							

COMMON_CONFIGURE_FLAGS := --program-dir=/usr
							

DEB_CONFIGURE_SCRIPT_ENV += BUILDOPT="someopt"
							

DEB_AC_AUX_DIR = $(DEB_SRCDIR)/autoconf
							

# these are the defaults CDBS provides
DEB_MAKE_INSTALL_TARGET := install DESTDIR=$(DEB_DESTDIR)
DEB_MAKE_CLEAN_TARGET := distclean
DEB_MAKE_CHECK_TARGET :=

# example to work around dirty makefile
DEB_MAKE_INSTALL_TARGET := install prefix=$(CURDIR)/debian/tmp/usr

# example with nonexistent install rule for make
DEB_MAKE_INSTALL_TARGET :=

# example to activate check rule
DEB_MAKE_CHECK_TARGET := check

# overriding make-only environment variables :
# (should never be necessary in a clean build system)
# (example borrowed from the bioapi package)
DEB_MAKE_ENVVARS    := "SKIPCONFIG=true"
							

# global configure options
DEB_CONFIGURE_EXTRA_FLAGS = --enable-gnutls

# per flavor configure options
DEB_CONFIGURE_EXTRA_FLAGS_full = --enable-gtk --enable-pam
DEB_CONFIGURE_EXTRA_FLAGS_nox = --enable-pam
DEB_CONFIGURE_EXTRA_FLAGS_light = --disable-unicode
DEB_CONFIGURE_EXTRA_FLAGS += $(DEB_CONFIGURE_EXTRA_FLAGS_$(cdbs_make_curflavor))
							

This class is intended to handle build systems using CMake.

To use this class, add this line to your debian/rules:

include /usr/share/cdbs/1/class/cmake.mk
						

This class is an extension of the Makefile class, calling cmake in DEB_SRCDIR with classic parameters and then calling make. In the call to cmake, the install prefix and path to CC/CXX as well as CFLAGS/CXXFLAGS are given automatically. You can pass extra arguments using DEB_CMAKE_EXTRA_FLAGS, and in strange cases where you need a special configuration you can override the default arguments using DEB_CMAKE_NORMAL_ARGS.

This class is intended to handle build systems using qmake, mostly used to build Qt applications.

To use this class, add this line to your debian/rules:

include /usr/share/cdbs/1/class/qmake.mk
						

This class is an extension of the Makefile class, calling qmake in DEB_BUILDDIR with classic parameters and then calling make. In the call to qmake, the path to CC/CXX as well as CPPFLAGS/CFLAGS/CPPFLAGS/CXXFLAGS are given automatically. Configuration options can be given using DEB_QMAKE_CONFIG_VAL (resulting in adding content to CONFIG), the later defaulting to nostrip if this option is set in DEB_BUILD_OPTIONS.

This class is intended to handle build systems using SCons, which is an alternative to make.

To use this class, add this line to your debian/rules:

include /usr/share/cdbs/1/class/scons.mk
						

The class takes care to invoke SCons and cleanup things afterwards. You can setup a few parameters:

# options for ALL targets (in addition to the DEB_SCONS_*_OPTIONS variables)
DEB_SCONS_OPTIONS = useALSA=1

# you can override the default build target (empty)
DEB_SCONS_BUILD_TARGET = 
# options for the build target
DEB_SCONS_BUILD_OPTIONS = useGettext=1

# you can override the default install target ("install")
DEB_SCONS_INSTALL_TARGET = install devel-install
# options for the install target
DEB_SCONS_INSTALL_OPTIONS = instdir=$(CURDIR)/debian/tmp

# you can override the default clean target (.)
DEB_SCONS_CLEAN_TARGET = fullclean

# activate the check target if set to the target name
DEB_SCONS_CHECK_TARGET = testsuite
						

This class can manage Perl builds using ExtUtils::MakeMaker (Makefile.PL) automatically.

To use this class, add this line to your debian/rules:

include /usr/share/cdbs/1/class/perl-makemaker.mk
						

You can customize build options like this:

# add custom MakeMaker options
DEB_MAKEMAKER_USER_FLAGS = --with-ipv6
						

As this class is a subclass of the makefile class, you can override the DEB_MAKE_* variables, but it should not be needed. Also beware DEB_BUILDDIR must match DEB_SRCDIR for this build system.

This class can manage Perl builds using Module::Build (Build.PL) automatically.

The following parameters can be overridden:

# these are the defaults CDBS provides
DEB_PERL_BUILD_TARGET = build
DEB_PERL_CHECK_TARGET = test
DEB_PERL_INSTALL_TARGET = install
DEB_PERL_CLEAN_TARGET = realclean

# add your custom parameters if the defaults do not suits you
DEB_PERL_CHECK_FLAGS = fulltestsuite=1
DEB_PERL_CONFIGURE_FLAGS = destdir=$(CURDIR)/build/stuff
						

Also beware DEB_BUILDDIR must match DEB_SRCDIR for this build system.

If you included the debhelper class, it can take care of calling dh_perl. Have a look at Perl-specific debhelper options described here.

Extra variables you can use in your debian/rules:

This class can manage common Python builds using distutils automatically.

To use this class, add these lines to your debian/rules:

# Don't forget to declare DEB_PYTHON_SYSTEM before this line
include /usr/share/cdbs/1/class/python-distutils.mk
						

You can customize build options like this:

############## These variables have not changed (same in the old and new policy)

# change the Python build script name (default is 'setup.py')
DEB_PYTHON_SETUP_CMD := install.py

# clean options for the Python build script
DEB_PYTHON_CLEAN_ARGS = -all

# build options for the Python build script
DEB_PYTHON_BUILD_ARGS = --build-base="$(DEB_BUILDDIR)/specific-build-dir"

# common additional install options for all binary packages
#   ('--root' option is always set)
DEB_PYTHON_INSTALL_ARGS_ALL = --no-compile --optimize --force
						

Complete debian/rules example using python-support for a module (editobj):

#!/usr/bin/make -f
# -*- mode: makefile; coding: utf-8 -*-

include /usr/share/cdbs/1/rules/debhelper.mk
DEB_PYTHON_SYSTEM = pysupport
include /usr/share/cdbs/1/class/python-distutils.mk
include /usr/share/cdbs/1/rules/patchsys-quilt.mk


DEB_COMPRESS_EXCLUDE := .py


$(patsubst %,install/%,$(cdbs_python_packages))::
        mv debian/$(cdbs_curpkg)/usr/lib/python*/site-packages/editobj/icons \
                debian/$(cdbs_curpkg)/usr/share/$(cdbs_curpkg)

$(patsubst %,binary-install/%,$(cdbs_python_packages))::
        find debian/$(cdbs_curpkg)/usr/share/ -type f -exec chmod -R a-x {} \;
						

For a Python module using autotools, it may be convenient to use this class, which is a subclass of the generic autotools class. It currently complement the DEB_CONFIGURE_SCRIPT_ENV variable with the PYTHON parameter, and adds needed build dependencies if debian/control management is activated. Moreover, if the package is to be built for multiple Python versions, then the multiple "flavors" build is automatically activated (DEB_MAKE_FLAVORS is set accordingly, but still can be overridden is needed).

To use this class, add this line to your debian/rules:

include /usr/share/cdbs/1/class/python-autotools.mk
						

This class can manage activity extensions for the Sugar Learning Platform (originally developed for the One Laptop per Child XO-1 netbook) automatically.

To use this class, add these lines to your debian/rules:

include /usr/share/cdbs/1/class/python-sugar.mk

# Compulsory: Sugar branches supported by this activity extension
DEB_SUGAR_BRANCHES = 0.84 0.86
						

You can customize build options like this:

############## These variables are additions for the new policy

# packages holding the collapsed content of all supported versions
# CDBS defaults to the first non -doc/-dev/-common package listed in "debian/control"
# this variable allows to override automatic detection
DEB_PYTHON_MODULE_PACKAGES = mypyapp

# list of private modules directories (for all binary packages) (needed to automatically handle bytecompilation)
DEB_PYTHON_PRIVATE_MODULES_DIRS = /usr/share/mypyapp/my-pv-module
# or for a specific binary package
DEB_PYTHON_PRIVATE_MODULES_DIRS_python-stuff-client = /usr/share/mypyapp/client-pv-module

# overrides the default Python installation root directory
DEB_PYTHON_DESTDIR = $(CURDIR)/debian/python-stuff
						

You may use some read-only (meaning you MUST NOT alter them) variables in your debian/rules:

This class can manage common setup.rb installer automatically.

To use this class, install the ruby-pkg-tools package, and add this line to your debian/rules:

include /usr/share/ruby-pkg-tools/1/class/ruby-setup-rb.mk
						

It can handle the following debhelper commands automagically:

Most ruby packages are architecture all, and then don't need being build for multiple ruby versions; your package should then be called 'libfoo-ruby' or 'foo' and CDBS would automatically use the current Debian ruby version to build it. If your package contains a compiled part or a binding to an external lib, then you will have packages named 'libfoo-ruby1.6', 'libfoo-ruby1.8', and so on, then CDBS would automatically build each package with the corresponding ruby version. In this case, don't forget to add a 'libfoo-ruby' convenience dummy package depending on the current Debian ruby version. If you have documentation you want split into a separate package, then call it 'libfoo-ruby-doc'. If this is Rdoc documentation, you may want to include the debhelper class, as explained before, to have it generated and installed automagically.

You can customize build options like this:

# force using a specific ruby version for build
# (should not be necessary)
DEB_RUBY_VERSIONS := 1.9

# use ancestor
DEB_RUBY_SETUP_CMD := install.rb

# config options for the ruby build script
# (older setup.rb used --site-ruby instead of --siteruby)
DEB_RUBY_CONFIG_ARGS = --site-ruby=/usr/lib/ruby/1.9-beta
						

If you are part of the Ruby Extras Team, or having the Team as Uploaders, and you feel bored maintaining the list of developers, this rule is made for you.

To use this class, install the ruby-pkg-tools package, and add this line to your debian/rules:

include /usr/share/ruby-pkg-tools/1/rules/uploaders.mk
						

Rename your debian/control file to debian/control.in and run the clean rule (./debian/rules clean) to regenerate the debian/control file, replacing the @RUBY_EXTRAS_TEAM@ (@RUBY_TEAM@ is deprecated) tag with the list of developers automatically.

This class adds a make environment variable : GCONF_DISABLE_MAKEFILE_SCHEMA_INSTALL = 1 (''This is necessary because the Gconf schemas have to be registered at install time. In the case of packaging, this registration cannot be done when building the package, so this variable disable schema registration in make install. This procedure if deferred until gconftool-2 is called in debian/postinst to register them, and in debian/prerm to unregister them. The dh_gconf script is able to add the right rules automatically for you.'')

It can handle the following debhelper commands automagically:

Moreover it adds some more clean rules to remove:

To use it, just add this line to your debian/rules, after the debhelper class include:

include /usr/share/cdbs/1/class/gnome.mk
						

For more information on GNOME specific packaging rules, look at the Debian GNOME packaging policy.

If you install the extra gnome-pkg-tools package, you will have extra rules and tools used by the GNOME Team for their packages. You should really have a look to the package documentation for additional information (mostly in /usr/share/doc/gnome-pkg-tools/README.Debian.gz).

If you are part of the GNOME Team, or having the Team as Uploaders, and you feel bored maintaining the list of uploaders, add this line to your debian/rules:

include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk
						

Rename your debian/control file to debian/control.in and run the clean rule (./debian/rules clean) to regenerate the debian/control file, replacing the '@GNOME_TEAM@' tag with the list of developers automatically.

ifneq (, $(DEB_AUTO_UPDATE_DEBIAN_CONTROL))
clean::
  sed -i "s/@cdbs@/$(CDBS_BUILD_DEPENDS)/g" debian/control
endif
						

This rule uses licensecheck (provided by devscripts) to check the debian/copyright file.

You need to create the empty file debian/copyright_hints (with touch) to activate this feature and get a report at the beginning of the build. If you set DEB_COPYRIGHT_CHECK_STRICT, the build will fail if it could not be run or problems were found by licensecheck.

You can customize the licensecheck parameters using DEB_COPYRIGHT_CHECK_ARGS, and the files to check for copyright information using DEB_COPYRIGHT_CHECK_REGEX and DEB_COPYRIGHT_CHECK_IGNORE_REGEX.

This rule uses dh_buildinfo (provided by dh-buildinfo), a tool to track package versions used to build a package.

It will generate a debian/buildinfo.gz file, which will be automatically installed in /usr/share/doc/package.

This rule is intended to avoid missing new files in a new software version, to allow the maintainer to check the list of not-installed files. This is useful when multiple binary packages are created and things may be lost in debian/tmp.

The rule must be called manually, after a build with the -nc dpkg-buildpackage option (to avoid cleaning the debian directory):

fakeroot debian/rules list-missing
						

It generates a list of installed files debian/cdbs-install-list found in debian/tmp and a list of files installed in the package (or ignored) debian/cdbs-package-list, then display the ones missing in the package. You can add a list of files to ignored, because you want to remember you wanted them excluded, in debian/not-installed. If you set DEB_BUILDINFO_STRICT, the build will fail if it could not be generated.

debian/rules:

#!/usr/bin/make -f

include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/rules/utils.mk
include /usr/share/cdbs/1/class/gnome.mk
include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk
include /usr/share/gnome-pkg-tools/1/rules/gnome-version.mk
-include /usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk

LDFLAGS += -Wl,-z,defs -Wl,-O1 -Wl,--as-needed

DEB_CONFIGURE_EXTRA_FLAGS += \
                        --disable-scrollkeeper \
                        --with-in-process-applets=all
ifneq ($(DEB_BUILD_GNU_SYSTEM),gnu)
        DEB_CONFIGURE_EXTRA_FLAGS += --enable-eds
endif

DEB_DH_MAKESHLIBS_ARGS_libpanel-applet2-0 += -V"libpanel-applet2-0 (>= 2.28.0)"
DEB_DH_MAKESHLIBS_ARGS_gnome-panel += --no-act

binary-install/gnome-panel::
        chmod a+x debian/gnome-panel/usr/lib/gnome-panel/*

binary-install/gnome-panel-data::
        find debian/gnome-panel-data/usr/share -type f -exec chmod -R a-x {} \;
        cd debian/gnome-panel-data/usr/share/gconf && \
                mkdir defaults && \
                mv schemas/panel-default-setup.entries \
                   defaults/05_panel-default-setup.entries

binary-install/libpanel-applet2-doc::
        find debian/libpanel-applet2-doc/usr/share/doc/libpanel-applet2-doc/ -name ".arch-ids" -depth -exec rm -rf {} \;
						

debian/rules:

#!/usr/bin/make -f

include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/gnome.mk
include /usr/share/gnome-pkg-tools/1/rules/uploaders.mk
include /usr/share/gnome-pkg-tools/1/rules/gnome-version.mk
include /usr/share/gnome-pkg-tools/1/rules/patch-translations.mk
-include /usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk

GNOME_MODULE := gdm

DEB_CONFIGURE_SCRIPT_ENV += X_PATH="/usr/bin" \
                            X_SERVER_PATH="/usr/bin" \
                            X_SERVER="/usr/bin/Xorg"

ifeq (linux,$(DEB_HOST_ARCH_OS))
    DEB_CONFIGURE_SCRIPT_ENV += X_CONFIG_OPTIONS="-audit 0 -novtswitch"
else
    DEB_CONFIGURE_SCRIPT_ENV += X_CONFIG_OPTIONS="-audit 0"
endif

DEB_CONFIGURE_EXTRA_FLAGS += --disable-scrollkeeper \
                --enable-ipv6=yes \
                --with-at-spi-registryd-directory=/usr/lib/at-spi \
                --with-default-path=/usr/local/bin:/usr/bin:/bin:/usr/games \
                --with-custom-conf=/etc/gdm3/daemon.conf \
                --with-sysconfsubdir=gdm3 \
                --with-working-directory=/var/lib/gdm3 \
                --with-xauth-dir=/var/run/gdm3 \
                --with-pid-file=/var/run/gdm3.pid \
                --with-log-dir=/var/log/gdm3 \
                --with-screenshot-dir=/var/run/gdm3/greeter \
                --with-defaults-conf=/usr/share/gdm/defaults.conf \
                --with-user=Debian-gdm --with-group=Debian-gdm \
                --with-pam-domain=gdm3

DEB_MAKE_EXTRA_ARGS += authdir=/var/lib/gdm3

ifeq (linux,$(DEB_HOST_ARCH_OS))
        DEB_CONFIGURE_EXTRA_FLAGS += --with-selinux
endif


DEB_DH_INSTALLINIT_ARGS := --noscripts

binary-install/gdm3::
        chmod 755 debian/gdm3/usr/share/gdm/gdmXnestWrapper
        mv debian/gdm3/usr/share/applications/gdmsetup.desktop \
                debian/gdm3/usr/share/gdm/applications/
        rmdir debian/gdm3/usr/share/applications
        mv debian/gdm3/usr/sbin/gdm-binary debian/gdm3/usr/sbin/gdm3
        cd debian/gdm3/usr/sbin && rm -f gdm-restart gdm-stop gdm-safe-restart
        chmod 755 debian/gdm3/etc/gdm3/Xsession
        dh_installpam -pgdm3 --name=gdm3-autologin
        rm -rf debian/gdm3/var/lib/gdm3/.g*
        rm -rf debian/gdm3/var/run
        rm -f debian/gdm3/usr/sbin/gdm
        rm -f debian/gdm3/etc/pam.d/gdm
        rm -f debian/gdm3/etc/pam.d/gdm-autologin
        cd debian/gdm3/usr/share/gdm/greeter-config && \
                mv session-setup.entries 10_upstream.entries

INFILES := $(wildcard debian/*.desktop.in)
OUTFILES := $(INFILES:.desktop.in=.desktop)

%.desktop: %.desktop.in
        intltool-merge -d debian/po-up $< $@

build/gdm3:: $(OUTFILES)

MANPAGES := $(patsubst %.pod,%,$(wildcard debian/*.pod))

common-build-arch:: $(MANPAGES)

clean::
        rm -f $(MANPAGES)
        rm -f $(OUTFILES)

%: %.pod
        pod2man --section=$(shell echo $@ | sed 's/.*\.//') \
                --release="GNOME $(DEB_GNOME_VERSION)" \
                --center="Debian GNU/Linux" \
                $< \
                | sed -e 's/debian:://' >$@