Hi, I am almost done with this packaging work. To sum up:
* There are 3 binary packages: code-aster, code-aster-mpi-engine, code-aster-tests.
* Everything is installed in /usr/lib/aster or /usr/share/aster following upstream (instead of /usr/{lib,share}/codeaster as previously). As a results, as_run (from astk packages) will not find Aster configuration. To circumvent this, I added a symlink /usr/share/aster → /usr/lib/codeaster/STABLE so that astk can be used unmodified.
* I had to move the Python library into /usr/lib/aster (instead of /usr/lib/pythonX.Y/dist-packages where the build system would have put it) because it would have cluttered the latter place otherwise (aster does not have a namespace); it makes sense in general because this library is essentially private.
* Waf binary is unpacked following instructions from https://wiki.debian.org/UnpackWaf (leading to a +dfsg1 source package).
* There is a few other patches to the build system, so that it behaves nicely in a Debian build (e.g. destdir is debian/tmp, ...)
The git repository includes upstream sources: http://anonscm.debian.org/gitweb/?p=debian-science/packages/aster.git Could someone review and let me know if this is OK? Regards, Denis -- Denis Laxalde Logilab http://www.logilab.fr -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
