[PROJ] PROJ 6RC2

[Even Rouault]

> I haven't rebuilt any reverse dependencies with PROJ 6.0.0 yet, as we
> can't transition to it in the near future anyway. But once that is done
> we should have an overview which package need to be patched to use
> proj_api.h or proj.h. Several of these packages aren't actively
> developed any more, so those patches will need to be contributed by
> someone experienced with the new APIs.

For the parts I maintain (with a lot of double quotes around """"maintain"""" 
for some of them),

- GDAL master / 2.5.0dev, to be released around May this year will require 
PROJ 6 (GDAL 2.4 should probably already work fine with PROJ 6, since it uses 
proj.h, but I didn't test)

- libgeotiff master / 1.5.0dev, to be probably released around the same time 
of GDAL 2.5, will require PROJ 6. Current versions should likely work fine 
since using proj_api.h if ACCEPT_USE_OF_DEPRECATED_PROJ_API_H is defined.

- the next version of shapelib will likely see its PROJ dependency removed 
(only affects the contrib area) since I don't care about it:
https://lists.osgeo.org/pipermail/shapelib/2019-February/000645.html

- the next version of OGDI will likely see its PROJ dependency removed for the 
same reason (it still uses project.h)
https://groups.yahoo.com/neo/groups/ogdidev/conversations/messages/314

- regarding MapServer, no immediate plan for action as far as I'm concerned. 
It uses proj_api.h so ACCEPT_USE_OF_DEPRECATED_PROJ_API_H can be used for now. 
Perhaps upgrading to proj.h would be a good topic for the OSGeo code sprint 
for those who can attend.

Even

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com