ansible/packaging/debian/rules

#!/usr/bin/make -f
# -- makefile --

DEB_PYTHON2_MODULE_PACKAGES=ansible ansible_test
#DEB_PYTHON_INSTALL_ARGS_ALL="--install-purelib=/usr/lib/python2.7/site-packages/"
DEB_PYTHON_DISTUTILS_INSTALLDIR_SKEL = /usr/lib/@PYTHONBINARY@/dist-packages/

include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/python-distutils.mk

# dist-packages for the modern distro, site-packages for the older (e.g: Ubuntu 14.04)
ifeq ($(shell lsb_release -cs), precise)
  export ANSIBLE_CRYPTO_BACKEND = pycrypto
endif
ifeq ($(shell lsb_release -cs), trusty)
  export ANSIBLE_CRYPTO_BACKEND = pycrypto
endif
Initial debian packaging 2012-04-18 18:17:35 +02:00			`#!/usr/bin/make -f`
			`# -- makefile --`

debian: prepare the ansible-test package - Generate an extra package for `ansible-test`. - Manually install the files because CDBS get confused by our two Python packages - Refresh the package descriptions to match what is done with the RPM 2019-09-04 01:50:17 +02:00			`DEB_PYTHON2_MODULE_PACKAGES=ansible ansible_test`
debian: install lib in dist-packages (#64412) On Ubuntu Precise and Trusty, the build was failing because the Ansible libs were installed in /usr/lib/python2.7/site-packages. According to the Debian Policy (2.5), they should actually be install in /usr/lib/python2.7/dist-packages This is also CDBS default behaviour since 0.4.131. See: https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html Closes: #64160 2019-11-05 16:45:05 +01:00			`#DEB_PYTHON_INSTALL_ARGS_ALL="--install-purelib=/usr/lib/python2.7/site-packages/"`
			`DEB_PYTHON_DISTUTILS_INSTALLDIR_SKEL = /usr/lib/@PYTHONBINARY@/dist-packages/`
migrate to dh-python 2016-03-17 18:13:39 +01:00
Initial debian packaging 2012-04-18 18:17:35 +02:00			`include /usr/share/cdbs/1/rules/debhelper.mk`
			`include /usr/share/cdbs/1/class/python-distutils.mk`
Use pycrypto backend, rather than python-cryptography, on Ubuntu Trusty 2017-07-12 16:46:26 +02:00
debian: install lib in dist-packages (#64412) On Ubuntu Precise and Trusty, the build was failing because the Ansible libs were installed in /usr/lib/python2.7/site-packages. According to the Debian Policy (2.5), they should actually be install in /usr/lib/python2.7/dist-packages This is also CDBS default behaviour since 0.4.131. See: https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html Closes: #64160 2019-11-05 16:45:05 +01:00			`# dist-packages for the modern distro, site-packages for the older (e.g: Ubuntu 14.04)`
Use pycrypto backend, rather than python-cryptography, on Ubuntu Precise 2018-02-19 12:24:53 +01:00			`ifeq ($(shell lsb_release -cs), precise)`
			`export ANSIBLE_CRYPTO_BACKEND = pycrypto`
			`endif`
Fix pycrypto backend setting to work when multiple distros are specified in DEB_DIST 2017-07-12 23:28:56 +02:00			`ifeq ($(shell lsb_release -cs), trusty)`
Use pycrypto backend, rather than python-cryptography, on Ubuntu Trusty 2017-07-12 16:46:26 +02:00			`export ANSIBLE_CRYPTO_BACKEND = pycrypto`
			`endif`