Le 02/10/2014 14:29, heroxbd@gmail.com a écrit :
>
> The casa table format is open, so the binary generated data can be
> converted back to ascii if desired. Therefore the transparency issue is
> not that severe.
>
Hi,
Ole is right: per Debian Policy (§2.1), if the binary data are produced
from ASCII files, you must distribute those ASCII files as source code
and build the binary version in debian/rules.
If you can't do that, casacore-data will go non-free. If casacore-data
goes to non-free and casacore depends or recommends casacore-data, then
casacore goes to contrib instead of main.
In the context of data which are a representation of a physical process,
the definition of "source code" requires some interpretation, but in the
process you describe, the binary form is clearly not the source.
> The difficulty does not lie only in circular dependency. The unit tests
> of casacore use ephemerides/VGEO and geodetic/{TAI_UTC,IGRF}. The
> script of measuresdata.csh from casacore-data only generates
> geodetic/{IERSeop{2000,97},IERSpredict{,2000},TAI_UTC}. I am wondering
> if Gijs knows how to generate ephemerides/VGEO and geodetic/IGRF.
>
> That's why I would go for uploading casacore tables (open-binary data)
> first
You can do that, sure. To non-free.
> and then figure out how to build them from ascii sources. The
> latter is complex enough, and it is not necessary to block the former.
Kind regards, Thibaut.
Attachment:
signature.asc
Description: OpenPGP digital signature