blob: e46a7337d46da3fd100022ca24802a5fece39ec7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
|
#!/usr/bin/make -f
# see FEATURE AREAS in dpkg-buildflags(1)
export DEB_BUILD_MAINT_OPTIONS = hardening=+all
# Link against all needed libraries (cf. Policy 10.2)
export DEB_LDFLAGS_MAINT_APPEND=-Wl,-z,defs
export deb_systemdsystemunitdir = $(shell pkg-config --variable=systemdsystemunitdir systemd | sed s,^/,,)
# Ubuntu/i386 shrank into a compatibility layer not carrying the
# dependencies of some of our binary packages (#948379):
ifeq ($(shell dpkg-vendor --query vendor)/$(DEB_HOST_ARCH), Ubuntu/i386)
UBUNTU_EXCLUDES = \
-Npacemaker \
-Npacemaker-cli-utils \
-Npacemaker-remote \
-Npacemaker-resource-agents
endif
%:
dh $@ $(UBUNTU_EXCLUDES)
override_dh_autoreconf:
dh_autoreconf ./autogen.sh
# Explicit BASH_PATH makes build reproducible on merged-usr vs non-merged:
override_dh_auto_configure:
dh_auto_configure -- --disable-static \
BASH_PATH=/bin/bash \
PYTHON=/usr/bin/python3 \
--enable-systemd \
--with-cibsecrets \
--with-configdir=/etc/default \
--with-initdir=/etc/init.d \
--libexecdir=/usr/lib
# because the daemon executables and Nagios plugins don't need multiarch paths
override_dh_auto_build-indep:
dh_auto_build
$(MAKE) -C doc doxygen
override_dh_installdocs:
dh_installdocs -A README.markdown
# Move test package documentation to its canonical place:
execute_after_dh_installdocs-indep:
mv --no-clobber \
debian/pacemaker-cts/usr/share/pacemaker/tests/README.md \
debian/pacemaker-cts/usr/share/doc/pacemaker-cts
override_dh_installinit:
# Upstream provides pacemaker and pacemaker-remote init files,
# we dh_install them and force the maintainer script modifications here:
dh_installinit --onlyscripts --no-restart-after-upgrade -p pacemaker
dh_installinit --onlyscripts --no-restart-after-upgrade -p pacemaker-remote --name=pacemaker_remote
override_dh_installsystemd:
dh_installsystemd --no-restart-after-upgrade
|