Heads-up: libdap and libnc-dap updates

[Patrice Dumas]

On Fri, Sep 05, 2008 at 08:22:33AM -0600, orion at cora.nwra.com wrote:
> 
> libnc-dap (shouldn't need work, right?):

No, but a rebuild should remove unneeded dependencies if there are some.
However, if there is an (unneeded) dependency on libdap itself, which was 
the case before, they will need a rebuild if there is no compat package. 

> grads/grads.spec:BuildRequires:  libnc-dap-devel
> ncl/ncl.spec:BuildRequires:  g2clib-devel, libnc-dap-devel, librx-devel,
> atlas-devel
> nco/nco.spec:BuildRequires:  netcdf-devel, libnc-dap-devel
> octave-forge/octave-forge.spec:BuildRequires:  ImageMagick-c++-devel
> libnc-dap-devel pcre-devel gsl-devel
> 
> 
> Seems pretty small, and you already seem to maintain many (most) of them. 
> How hard would it be to port to the new libdap and just skip the compat
> package?  I've CC'ed Balint who maintains gdal.  I maintain ncl.

There is only gdal which is not maintained by me in the libdap
dependencies. But I will need to rebuild deverything using make
chain-build but this is not practical because there are many packages
to update at once.

Since this time it is more than a rebuild, I thought that doing a
compat-package would be more convenient (I use that compat package
locally since a long time now).

--
Pat