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

Bug#458812: ITP: aster -- Finite Element Analysis (FEA) software for engineering simulations



Hello,



> I would like to help in packaging the Code Aster software[1] for Debian.
Thanks for your interest in the packaging of Code Aster.
You are more than welcome to help. If it is not the case now, you could
join the Debian Science team and start to update the SVN repository. I
will be happy to upload your changes.
However, you should be aware of a license issue with metis-edf:
http://glaros.dtc.umn.edu/gkhome/node/686
To unblock, we should consider some uploads in non-free and contrib. 

About libaster, I added Nicolas as C/C (who is one of the person at the
origin of this project). I am aware he wants to have it in Debian.



> Some work is already done, in the debian-science svn repository there is packaging for the code aster engine and other tools and libraries[2]
> 
> This however has still some issues, in particular it doesn't build the mpi parallel version, but I've worked on this and I obtained a (more-or-less) working mpi package[3][4]
> 
> I would like to know what should be done to make those packages enter into the distribution, and see if I can help in this task; it has to be note however that, at the moment, code aster uses some tools and libraries that don't have a free license, e.g. the metis-edf library.
> 
> Another thing that should be discussed is the build system: CA has its own build system, but now there's also an effort (libaster[5]) to use waf instead. I haven't yet contacted the CA team to ask if they are planning to switch to waf or stick to their custom build system.
> If I'm gonna be the only one working on the packages, I'd rather stay on the CA's custom system - at least for now - because I know it, and also because I don't know waf at all; but if some other people will be helping, maybe using waf could be a better choice.
> 
> So... what should be done for the packaging? Can it enter in Debian even if it uses non-free tools? Maybe in non-free? Or it's preferred to (try to) build a cut-down version, but 100% open source?
> 
> Bye
> Andrea
> 
> [1] http://www.code-aster.org/
> [2] http://svn.debian.org/viewsvn/debian-science/packages/code-aster/
> [3] http://www.code-aster.org/wiki/doku.php?id=en:p02_install:debianpackages
> [4] http://www.code-aster.org/forum2/viewtopic.php?id=14953
> [5] http://www.libaster.org/
> 
> 





Reply to: