[Python-apps-team] Bug#522426: Info received ( Bug#522426: Bug#522426: Status on debian bug #522426 (Mercurial 1.2.1)?)

[Max Bowsher]

Dmitrijs Ledkovs wrote:
> --- debian/rules	(revision 2804)
> +++ debian/rules	(working copy)
> @@ -10,17 +10,15 @@
>  include /usr/share/cdbs/1/rules/debhelper.mk
>  include /usr/share/cdbs/1/rules/patchsys-quilt.mk
>  DEB_INSTALL_DOCS_ALL=
> +DEB_PYTHON_DESTDIR = $(CURDIR)/debian/$(cdbs_curpkg)
> +DEB_PYTHON_MODULE_PACKAGES = mercurial-common
>  
>  # These part must be run between dh_install and dh_pysupport
>  # So, they must be defined BEFORE including python-distutils.mk
> -binary-install/mercurial::
> -	# remove arch-independent python stuff
> -	find debian/mercurial/usr/lib \
> -		! -name '*.so' ! -type d -delete , \
> -		-type d -empty -delete
> -
>  binary-install/mercurial-common::
>  	# remove arch-dependent python stuff
> +	(cd debian/mercurial-common && find usr/lib \
> +		-name '*.so' | cpio -pmd ../mercurial/)
>  	find debian/mercurial-common/usr/lib \
>  		-name '*.so' ! -type d -delete , \
>  		-type d -empty -delete

Surely this is going to break horribly when building arch-specific
binary packages only?

What about simply adding:

DEB_PYTHON_MODULE_PACKAGES = mercurial mercurial-common

?

I agree the mention in the NEWS file that:
+    As its name indicates, the new variable may support multiple Python
+    packages in the future.

specifically "in the future" is slightly troubling, and some
clarification from the cdbs maintainers would probably be a good thing.

However, it seems to work fine, confirmed by diffing the produced binary
debs from a build with lenny-cdbs with those from a build with
squeeze-cdbs plus that one added line.

Max.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/python-apps-team/attachments/20090428/89bd17ed/attachment.pgp>