Re: netCDF Strategy
-----BEGIN PGP SIGNED MESSAGE-----
On 01/24/2015 05:47 PM, Ross Gammon wrote:
> 1. We claim in the changelog that Multi-Arch is enabled, but I am
> not sure we have done this fully according to
We have the files installing to the correct paths, but I can't see the
> "Multi-Arch" stanzas in d/control.
We have indeed not yet marked the packages. libnetcdf and the -dbg &
- -dev package should become Multi-Arch: same, whereas netcdf-bin should
become Multi-Arch: foreign.
> On 01/17/2015 01:02 AM, Sebastiaan Couwenberg wrote:
>> libCF is still TODO
> ITP: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775584
I have basic packaging ready for libCF, but we should decide on the
source package name. Initially I used just 'libcf' too, but then opted
to change it to 'netcdf-libcf' because it's so closely related to
netcdf in general, and because libcf is split out from the netcdf package.
Unfortunately there are only a couple of alpha and one beta release
published upstream, and it doesn't look very actively developed. So I
have my doubts about the usefulness of keeping libCF in Debian.
One of the outstanding issues I have with the libCF packaging is that
it builds both libcf.so.1 and libcf_src.so.1 and the difference is not
clear to me. libcf in netcdf 4.1.3 only has a single version of the
GPG Key ID: 4096R/E88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
-----END PGP SIGNATURE-----