Well, I'm back on this. I released a 0.50.1 with the proper fix and the clarification made by Sylvain about the licensing (LGPL).
Just check out from ftp site and/or pypi. I've updated Logilab's debian/rules. Thanks for your useful corrections. By my side, I only add a new Build-Depends on python-egenix-mxdatetime as new (or missing?) test dependancy. In the long term, concerning differences between our both versions of debian/rules, the important part for us is to keep compatibility for all flavours of Debian (and Ubuntu). Blockers appears with include directives as python.mk or dpatch.make since these files are not always existing on our larger target of distributions. Do you think It's possible to have old compatibility code into the official debian/rules or you want to keep it as clean as possible? FYI, the last remaining diff with our version is attached. Cordially, -- Julien JEHANNET LOGILAB, Paris (France) http://www.cubicweb.org CubicWeb, le cadriciel du web sémantique http://www.logilab.org Dépôt des logiciels libres conçus par Logilab http://www.logilab.fr Informatique scientifique & Gestion de connaissances
13a14,15
> include /usr/share/dpatch/dpatch.make
>
17,24d18
< -include /usr/share/python/python.mk
< ifeq (,$(py_sitename))
< py_sitename = site-packages
< py_libdir = /usr/lib/python$(subst python,,$(1))/site-packages
< py_sitename_sh = $(py_sitename)
< py_libdir_sh = $(py_libdir)
< endif
<
26c20
< build-stamp:
---
> build-stamp: patch-stamp
38a33
> rm -f $(CURDIR)/build/lib/logilab/__init__.py
44d38
< rm -f $(CURDIR)/build/lib/logilab/__init__.py
47c41
< clean:
---
> clean: unpatch
70c64
< ${py_setup_install_args}
---
> --install-layout=deb
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
