[gdal-dev] Regarding libkml driver

[Wolf Bergenheim]

On 11 August 2015 at 18:56, Sebastiaan Couwenberg <sebastic at xs4all.nl>
wrote:

> On 11-08-15 18:37, Kurt Schwehr wrote:
> > Wolf and I have joined in working on libkml.  We will be getting more
> > transitioned from the old code.google.com site to
> > https://github.com/google/libkml, will be pushing some general
> maintanence
> > patches and will be getting the pull request processed.  We look forward
> to
> > collaborating on future development of libkml.
>
> The renewed interest in libkml from Google sounds promising.
>
> Glad to hear it!


> What are your views on merging the work in the libkml/libkml fork back
> into google/libkml?
>
>
I'd like to merge back as much of the work that has gone into libkml/libkml
to google/libkml. Especially externalizing libraries.


> The switch to CMake and removal of the third party dependencies in favor
> of linking to system provided libraries solve the issues that required
> patches in the libkml Debian package in the past. I'd like to see these
> changes merged back into google/libkml to not loose these gains.
>
> These sound very interesting, and I'll look at them more closely, but on
the surface it looks good.


> Most importantly the final 1.3.0 libkml release is long overdue, it has
> been required for GDAL for many years now but many distributions still
> ship libkml 1.2 (Fedora removed libkml even because it was abandoned
> upstream). What do you think needs to be done to get the 1.3.0 release out?
>
>
Hmm. I think that we should first get to the point where we can merge the
libkml/libkml stuff back to google/libkml before we push out a new release,
in order to avoid confusion and mess.
Also we might want to call it libkml 2.0.0 so we don't really need to worry
about backwards compatibility.

--Wolf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20150812/9b009951/attachment.html>