[Build-common-hackers] Bug#606530: Bug#606530: packages build-depending on python-dev should not be built for non-default python version

[Jonas Smedegaard]

Hi Matthias,

On Fri, Dec 10, 2010 at 12:07:36AM +0100, Matthias Klose wrote:
>A package which build-depends on python-dev and not python-all-dev 
>should only be built with the default python version.

Is that a fact, or do you propose this behaviour?

Seems wrong to me to mandate such behaviour based on direct build 
dependencies.


>Both debhelper and cdbs now try to build for the intersection of the 
>installed and requested python versions (which only depends on the 
>installed pythonX.Y packages, but not the pythonX.Y-dev packages), and 
>then fail to build not finding e.g. headers in the non-default 
>pythonX.Y-dev package.

CDBS currently by default build for all variants of Python available at 
build time.  It is then the responsibility of the package maintainer to 
ensure that either build-dependencies for all those Python versions are 
satisified or to override the default behaviour and limit the Python 
variants worked on. And it is the responsibility of the Python team to 
provide sensible behaviours of the python-*dev packages.


>In the past we had the XS-Python-Version: current attribute for this 
>scenario, but that was ditched for reasons not entirely understood by 
>me.

CDBS provides helper tools for packaging, not (if we can avoid it) 
band-aid for lack of sensible logic in underlying build infrastructures.

I sugest you resolve Python build systems issues internally among the 
build infrastructures python-central python-support and python-default, 
and then tell us package helper folks what you came up with which we can 
then support from a higher altitude.


>Currently both debhelper and cdbs already parse build-dependencies to 
>decide whether to build -dbg packages or not.

I believe not.  CDBS parse debian/control, yes, but not package 
dependencies, only names of binary packages.


>So maybe this analysis should be extended to look for the python-dev 
>b-d, and in this case not to build the package for the non-default 
>python version, and only build for all supported python versions in the 
>presence of a python-all-dev dependency (or python-all-dbg, as this 
>depends on python-all-dev).

I really think this should be addressed the other way around: By 
defining rules for the package maintainers independently of CDBS or 
debhelper, and then when done encourage integration of the rules into 
CDBS and debhelper.


Kind regards,

  - Jonas

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

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/build-common-hackers/attachments/20101226/b372197f/attachment.pgp>