Il Mercoledì 26 Marzo 2014 10:07, Denis Laxalde ha scritto:
Hi,
>Andrea Palazzi a écrit :
>> So, the package is good, the only thing that should be changed, if we
>> want to upload the package as soon as possible, is that with this
>> packaging, code-aster-mpi-engine should depend on code-ast
Hi,
Andrea Palazzi a écrit :
So, the package is good, the only thing that should be changed, if we
want to upload the package as soon as possible, is that with this
packaging, code-aster-mpi-engine should depend on code-aster and not
vice-versa.
I don't understand why we'd want this. With the c
Hi,
sorry for the late asnwer, I've been busy in these days.
So, the package is good, the only thing that should be changed, if we want to
upload the package as soon as possible, is that with this packaging,
code-aster-mpi-engine should depend on code-aster and not vice-versa.
On the other ha
Yet another update: I rebased the packaging on the current stable
release (11.5.0 w.r.t. 11.4 at the time I started working on it).
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science
Hi,
Some other changes and Lintian warnings fixes:
- install the elements catalog in /usr/lib/aster as it is architecture
dependent.
- install the Python library in code-aster binary as it is not tied to
the underlying engine.
Regards.
--
Denis Laxalde
Logilab http://www.logilab.fr
Andrea Palazzi a écrit :
I propose to disable it for the moment and focus on getting a working
and lintian-clean package; then we can think about what to do with metis
and also work to build multiple versions.
That seems reasonable. Added two commits for this. Of course, some tests
will not pa
Hi,
I did some testing, and I can't build the packages in any way with libmetis or
libparmetis, but if I remove it from the build-deps I can make the packages.
I propose to disable it for the moment and focus on getting a working and
lintian-clean package; then we can think about what to do wi
On Tue, 2014-03-18 at 08:38 +0100, Denis Laxalde wrote:
> Hi,
>
> Andrea Palazzi a écrit :
> > - I'd really prefer to remove the libmetis dependency and keep it in
> > main and not in contrib; after all libmetis is not absolutely required (
> > the patch no_metis_default.diff was there to change t
Hi,
Andrea Palazzi a écrit :
- I'd really prefer to remove the libmetis dependency and keep it in
main and not in contrib; after all libmetis is not absolutely required (
the patch no_metis_default.diff was there to change the default
renumerator from metis to md ) , and I think that packages in
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 result
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
11 matches
Mail list logo
