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

Re: RFC: casacore-2.1.0-1 debian package





2016-05-10 14:54 GMT+02:00 Benda Xu <heroxbd@gentoo.org>:
Hi Gijs,

Gijs Molenaar <gijsmolenaar@gmail.com> writes:

>    Do you mean "libcasa-mirlib2" and friends? Are you suggesting they
>    should be named "libcasacore-mirlib2", or "casacore-mirlib2"?
>
> yes. Don't use the name casa.

Why does the upstream name its shared libraries libcasa_meas.so, etc.?

good question. I don't know. 


> no the story is more complex than that, but basically casa just uses
> casacore.

Could you point me more details about the history? 


I'm not completely sure, but I think it was called AIPS++ before, then forked by NRAO to become part of CASA. Then it was forked again to become CASACORE. 

 
Because casa is also
on our list to be packaged.

Good luck with that, it is a nightmare.  I tried it 2 years ago. basically casa is a huge tarball where they compile all their dependencies statically in. It uses a lot of deprecated (python) libraries. Dev activity is quite active, but not on the front of portability. The software is open source, but all development happens behind curtains, they don't have a public bug tracker for example.

I wrote a set of patches to get stuff sort of working on debian/ubuntu:

https://github.com/radio-astro-debian/casa-code-debian

They also bundle it with a forked/modified version of casacore.



--
Gijs Molenaar


Reply to: