Re: Bug#731211: aster: new upstream release, work in progress
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 contrib
are out of the auto-builder circuit. Moreover we all prefer 100% free
software ;-)
I agree that this Aster in Debian would be better with the non-free
dependency on libmetis. However, I actually had troubles during build
with scotch version of metis. I will look into this further, though.
- I would really like to have both the serial and mpi version available:
the serial version is faster if you're not running a cluster
I'm not opposed to having both versions but, again, I had trouble
building the non-mpi flavor. So I actually chose the simplest path to
having a working version of code-aster in Debian.
- then, if you have two (or more) versions, you'll need a script to
update the information in /etc/codeaster/aster ; note that this file is
partly a status file - that is, its content represents some kind of
status, in our case the available versions: this is what the
postinst/postrm scripts were supposed to do
Not sure how soon we'll have two (or more) versions of code-aster.
- not sure if it's automatically done somewhere, but on 64 bit
architectures you'll have to pass -D_MED_USE_SHORT_INT to the compiler
to be able to open med files
This is done automatically, there's a call to 'check_sizeof_med_int' at
configure step.
PS: the package fails to build on my system with git-buildpackage - it
seems it can't find some metis file, but I have installed libmetis-dev.
It also fails with git-buildpackage/cowbuilder because libmetis is in
non-free... how do you build the package?
Either using debian/rules binary or dpkg-buildpackage or sbuild. It
builds fine on Sid and Wheezy, as well as in sbuild's chroots.
I'm not surprised git-buildpackage does not work as is, since I didn't
figure out yet what the git repository layout should be.
Thank you for your comments !
Regards.
--
Denis Laxalde
Logilab http://www.logilab.fr
Reply to: