On 11-05-26 at 05:10pm, Olivier Aubert wrote:
> Thanks for the examples (lash does not seem to have switched though).
> However, looking at them does not help: the package currently in git at
> git://git.debian.org/git/pkg-multimedia/advene.git
> compiles perfectly with pysupport.  If I remove the 
> line, CDBS does not seem to grok that it is a python package, and does
> not invoke dh_python2 at all (although it even invokes dh_perl at some
> stage).
> What are the heuristics or parameters used by CDBS to determine that it
> should call dh_python2?

Packages are resolved in CDBS snippet python-vars.mk.in inherited by all 
python-* snippets:

> # By default the "python2" and "python3" packaging systems are used
> # Possible alternatives are "pysupport" or "pycentral"
> # With "python2" and "python3", all likely packages are used by default
> # These are tied together: Set one and default is none for the other
> # NB! override needs to be done _before_ including this file!
> # With "pysupport" and "pycentral", first likely package in
> # 'debian/control' is used by default
> # NB! override needs to be done _before_ including this file!

The "likely packages" are those named python-* or python3-*, following 
Debian Python Policy regarding Python module packages.

If your package contains an app (not a module) then explicitly list the 
package name in DEB_PYTHON2_MODULE_PACKAGES and it will be handled by 
the python2 install helper, or in DEB_PYTHON3_MODULE_PACKAGES for 

Originally the old install helpers had same logic, but that got horribly 
broken during the rushed transition to Python Policy 2 :-(

 - Jonas

 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to