[gentoo-science] CASA vs casacore

[gentoo-science] CASA vs casacore

[Joseph Booker]

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

Hello,

I've been trying to package casa and its dependencies with some amount of
success. It requires a few new packages (including a version of xerces-c
that was removed for security reasons), but it requires a different
implementation of casacore then is currently in the main tree.

Specifically, casacore from https://code.google.com/p/casacore has been
forked with additions made to the interface. This fork is only available
from an svn repo, and the only "releases" are tags when a new version of
casa is released.

The current casacore ebuild grabs the last release from
https://code.google.com/p/casacore . This is two years old and greatly
out-of-date. The "trunk" is too out of date, but the nrao-nov12 appears to
merge in the changes from casa every once in awhile.

I'm wondering if the current casacore ebuilds should be replaced with ones
that pull from the "releases" from nrao, or if I should make new (blocking)
casa-casacore ebuilds for this fork.

Thanks,
Joseph Booker

[-- Attachment #2: Type: text/html, Size: 1224 bytes --]

Re: [gentoo-science] CASA vs casacore

[Sébastien Fabbro]

On Thu, May 15, 2014 at 4:34 PM, Joseph Booker <joe@neoturbine.net> wrote:
>
> I've been trying to package casa and its dependencies with some amount of
> success. It requires a few new packages (including a version of xerces-c
> that was removed for security reasons), but it requires a different
> implementation of casacore then is currently in the main tree.
>
> Specifically, casacore from https://code.google.com/p/casacore has been
> forked with additions made to the interface. This fork is only available
> from an svn repo, and the only "releases" are tags when a new version of
> casa is released.
>
> The current casacore ebuild grabs the last release from
> https://code.google.com/p/casacore . This is two years old and greatly
> out-of-date. The "trunk" is too out of date, but the nrao-nov12 appears to
> merge in the changes from casa every once in awhile.
>
> I'm wondering if the current casacore ebuilds should be replaced with ones
> that pull from the "releases" from nrao, or if I should make new (blocking)
> casa-casacore ebuilds for this fork.
>

Hi,

Probably best to contact casa and casacore upstream to see what the
differences and roadmaps are. It's possible that they might make our
life easier by unbundling and splitting the packages. The science
overlay would be a good place to maintain the casa version of
casacore.

Sebastien

Re: [gentoo-science] CASA vs casacore

[heroxbd]

Hello Joseph and Sébastien,

Sébastien Fabbro <bicatali@gentoo.org> writes:

> On Thu, May 15, 2014 at 4:34 PM, Joseph Booker <joe@neoturbine.net> wrote:
>>
>> I've been trying to package casa and its dependencies with some amount of
>> success. It requires a few new packages (including a version of xerces-c
>> that was removed for security reasons), but it requires a different
>> implementation of casacore then is currently in the main tree.
>>
>> Specifically, casacore from https://code.google.com/p/casacore has been
>> forked with additions made to the interface. This fork is only available
>> from an svn repo, and the only "releases" are tags when a new version of
>> casa is released.

FYI, the casacore teams is planning to roll out a tarball of 1.6.0 release

http://code.google.com/p/casacore/issues/detail?id=58#c4

>> [...]
>>
>> I'm wondering if the current casacore ebuilds should be replaced with ones
>> that pull from the "releases" from nrao, or if I should make new (blocking)
>> casa-casacore ebuilds for this fork.
>
> Probably best to contact casa and casacore upstream to see what the
> differences and roadmaps are. It's possible that they might make our
> life easier by unbundling and splitting the packages. The science
> overlay would be a good place to maintain the casa version of
> casacore.

+1

Cheers,
Benda