Update netcdf to 4.3.2

[durack1]

We are a couple of patch releases behind the netcdf latest (4.3.0 vs 4.3.2 - 4.3.3 is in RC2), I'll obtain the source tar balls and update UV-CDAT sources to point to the latest release..

@doutriaux1 @aashish24 want to assign this task as a 2.1 milestone? I also note that they've done some fairly heavy reorganizing of the tarball (http://www.unidata.ucar.edu/software/netcdf/docs/release_notes.html) and have fixed a bunch of bugs and updated all the dependencies (zlib 1.2.8, hdf 1.8.12), and the current 4.3.0 patch may need to be revisited too..

[durack1]

@doutriaux1 @aashish24 we might also want to pull these sources from their new git repo, rather than having to manage the source tar balls https://github.com/Unidata/netCDF-C

[doutriaux1]

heck no! too many issues with firewall, we need tarballs at least as a fallback.

[aashish24]

I think we need to have both. @doutriaux1 and I talked about fallback methods. I don't know if cmake supports that directly but probably we can modify that.

[doutriaux1]

@aashish24 I don't think there's a clear/clean way to do the fallback in cmake right now. Can Kitware look into it? Also we should use that opportunity to implement "mirror" servers so that we don't rely on LLNL_URL only.

[aashish24]

@doutriaux1 that's what I meant. We will look into it.

[durack1]

@doutriaux1 ok sources are updated at the ${LLNL_URL} these include:
netcdf-4.3.2.tar.gz 2fd2365e1fe9685368cd6ab0ada532a0
hdf5-1.8.13.tar.gz c03426e9e77d7766944654280b467289
zlib-1.2.8.tar.gz 44d667c142d7cda120332623eab69f40

I'll tweak the MD5 codes and patch numbers and submit a pull request

[durack1]

@doutriaux1 @aashish24 can you mark this as a 2.2 milestone please?

[durack1]

@doutriaux1 wanna add the enhancement label (for @chaosphere2112's readme: #913)