"to mu or not to mu"

FWIW: for mpi4py I decided to avoid hardcoding the suffix:

diff --git a/debian/rules b/debian/rules
index 0688ac2..54e761d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -54,10 +54,14 @@ override_dh_install:
        done
 
        : # Python 3
+ : # Can have python$$v symlink pointing to python3.?m or python3.?mu
+ : # see #700995 for more details.  So first look where it points to
+ : # and use that directory
        set -e; for v in $(PY3VERS); do \
        [ -d $(CURDIR)/debian/python3-mpi4py/usr/include/python$$v ] || \
-           mkdir -p $(CURDIR)/debian/python3-mpi4py/usr/include/python$$v; \
-           dh_link -ppython3-mpi4py 
usr/lib/python3/dist-packages/mpi4py/include/mpi4py 
usr/include/python$$v/mpi4py; \
+         pythonv_inc_dir=$$(readlink -f /usr/include/python$$v); \
+         mkdir -p $(CURDIR)/debian/python3-mpi4py$$pythonv_inc_dir; \
+         dh_link -ppython3-mpi4py 
usr/lib/python3/dist-packages/mpi4py/include/mpi4py 
$${pythonv_inc_dir#/}/mpi4py; \
        done
 
        : # share -dbg and normal package doc dirs


On Wed, 27 Feb 2013, Andreas Beckmann wrote:

> Hi,

> On 2013-02-27 11:07, Sébastien Villemot wrote:
> > +  * Install symlinks for Python 3 headers under /usr/include/python3.2mu 
> > (resp.
> > +    python3.2dmu) instead of /usr/include/python3.2 (resp. python3.2_d),
> > +    to avoid file versus symlink conflict. (Closes: #700994)

> > -   [ -d $(CURDIR)/debian/python3-numpy/usr/include/python$$i ] || \
> > -           mkdir -p $(CURDIR)/debian/python3-numpy/usr/include/python$$i; \
> > -           dh_link -ppython3-numpy 
> > usr/lib/python3/dist-packages/numpy/core/include/numpy 
> > usr/include/python$$i/numpy; \
> > +   [ -d $(CURDIR)/debian/python3-numpy/usr/include/python$${i}mu ] || \
> > +           mkdir -p 
> > $(CURDIR)/debian/python3-numpy/usr/include/python$${i}mu; \
> > +           dh_link -ppython3-numpy 
> > usr/lib/python3/dist-packages/numpy/core/include/numpy 
> > usr/include/python$${i}mu/numpy; \

> Did you look into using an up-to-date python3.2-dev to get the include
> path correct automatically?

> doko closed #700996 with:
> > python-bsddb3 (5.3.0-2) unstable; urgency=low
> >   * Build-depend on python3.2-dev (>= 3.2.3-7). Closes: #700996.


> Andreas

> _______________________________________________
> Python-modules-team mailing list
> [email protected]
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

-- 
Yaroslav O. Halchenko
http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
Postdoctoral Fellow,   Department of Psychological and Brain Sciences
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik        

_______________________________________________
Python-modules-team mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team

Reply via email to