Viewing file:  ap-build_dependencies.html (2.84 KB) -rw-r--r--
Select action/file-type:
 (+) | (+) |  (+) | Code (+) | Session (+) |  (+) | SDB (+) |  (+) |  (+) |  (+) |  (+) |  (+) |
Debian Python Policy - Build Dependencies
[ previous ]
[ Contents ]
[ 1 ]
[ 2 ]
[ 3 ]
[ 4 ]
[ 5 ]
[ A ]
[ B ]
[ C ]
[ next ]
Debian Python Policy
Appendix A - Build Dependencies
Build dependencies for Python dependent packages must be declared for every
Python version that the package is built for. The python-all-dev
should be used when building modules for any or all Python versions. To build
for a specific version or versions, Build-Depend on
pythonX.Y-dev.
Some applications and pure Python modules may be able to depend only on
python or python-all and not require the -dev
packages.
Build-Depend on at least:
Build-Depends: python2.3 (>= 2.3-1)
Build-Depends: python2.4 (>= 2.4-1)
Build-Depends: python (>= 2.3.5-7)
Build-Depends: python-all
Build-Depends: python2.3-dev (>= 2.3-1)
Build-Depends: python2.4-dev (>= 2.4-1)
Build-Depends: python-dev (>= 2.3.5-7)
Build-Depends: python-all-dev
If you use either python-support or python-central
you must additionally Build-Depend on those. If you are using
dh_python at all, you must Build-Depend on python, as
debhelper does not depend on it.
[ previous ]
[ Contents ]
[ 1 ]
[ 2 ]
[ 3 ]
[ 4 ]
[ 5 ]
[ A ]
[ B ]
[ C ]
[ next ]
Debian Python Policy
version 0.4.1.0
Neil Schemenauer nas@debian.org
Matthias Klose doko@debian.org
Gregor Hoffleit flight@debian.org
Josselin Mouette joss@debian.org
Joe Wreschnig piman@debian.org
|