[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#731211: aster: new upstream release, work in progress



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 w
ith this packaging, code-aster-mpi-engine should depend on code-aster and not vice-versa.
 
On the other hand, I think that the packaging scheme should stay as it was previously:  the code-aster package was originally meant to be a meta-package, just to allow to easlily install the whole thing with apt-get install code-aster; I think we should still follow this concept. So, move all arch-independent files (mostly python) in another package, like code-aster-common; move the elements file and other arch-dependant files common to the serial and parallel version to another package code-aster-elements, and leave the code-aster package as a metapackage.
Suggestions on better package scheme ( and naming ) naming are welcome :)

Other issues/enhancements/wishes:

- the code-aster package creates both /usr/lib/aster an /usr/lib/codeaster; the latter seems to be used just for a symlink from ../../share/aster . It's just a leftover of the old packaging, or CA looks for files in this path?
Note however that code-aster-run puts some files under /usr/lib/codeaster, so we shoult ideally take also care of code-aster-run and code-aster-gui packages.

- In the process, I'd like also to switch from svn to git.

- as_run doesn't work out of the box: it relies on having informations about available versions in the file /etc/codeaster/aster ; the script update-codeaster-engines takes care of this, it should be run on postinst/postrm scripts of the code-aster-*-engine packages.

- provide also the serial version

- a simple script to run the test cases would be nice... the .comm file that was used for this purpose has been removed from upstream, or it's just me that can't find it?

- we should fix libmetis in one way or another, either by adapting the sources to libmetis 5.1.0 (the metis documentation says something about this process) or by changing the default renumerator from METIS to something other, like MD, so that it can be compatible with comm files that doesn't specify the renumerator to be used.

- 11.5 is already out

- and I'd like to provide also testing/unstable versions

So, considering that the actual packages are empty, I propose to fix the dependency and upload the packages, then start working on enhancong the package.

Bye
Andrea


Il Venerdì 21 Marzo 2014 10:09, Denis Laxalde <denis.laxalde@logilab.fr> ha scritto:
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


--
To UNSUBSCRIBE, email to debian-science-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive:
[🔎] 532BFD49.8040602@logilab.fr">https://lists.debian.org/[🔎] 532BFD49.8040602@logilab.fr





Reply to: