Denis Laxalde a écrit :
I've push the current state of my current in a git repository (converted
from the svn one):
http://anonscm.debian.org/gitweb/?p=debian-science/packages/aster.git

Added a few more commits.

Currently, I'm able to build aster and to run tests (though with some adjustment to as_run, see below).

Now, I have a couple of issues that need to be resolved.

1. The previous packaging shipped the serial and MPI flavor of aster, currently I only build the MPI version (I am not even sure the serial version will work). Do we want to keep both version or could we only ship one, at least over a first phase ?

2. I don't build the -dbg and -dev binaries so far.

3. Why does the package installs into /usr/aster/codeaster, upstream just uses /usr/share/aster ?

4. I cannot use as_run (from code-aster-run binary. astk source) as is, I need to specify the option `--vers /usr/share/codeaster/`, maybe I also need to adjust this package.

Most of these questions actually boils down to whether we can step from the previous packaging and consider a simpler approach to begin with and eventually move towards something more complex once everything stabilizes. And if this approach is acceptable, is some sort of transition needed ?

Thanks,
Denis

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to