[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [DebianGIS] geos



hi steve,

while libgeos_c provides a solid c api, it is calling the changing c++
source, and may still differ internally for each c++ version.

moreover, the c api has no usage other than an interface to libgeos.

thus, i would suggest making, if possible, only one library
(libgeos.so.*), with the c api source linked in, and one package, as before.

this way, c++ programs will still call c++ interface, while newer c
programs will only use the stable c api, and will tolerate every change
in libgeos due to upgrades, etc.

best regards,

alex

Steve Halasz wrote:
> Hi,
> 
> I've imported the geos control files into alioth cvs and made DebianGIS
> the maintainer. Geos 2.2 has introduced a c api and I want to make sure
> I get the split right. It now has libgeos_c.so.1.0.1 and
> libgeos.so.2.2.1. So these are pretty easy to split into libgeosc1 and
> libgeos2c2a packages. I'm less sure what to do with the -dev package.
> There is a geos_c.h header and a geos.h header. But there are a number
> of presumably shared .h files and geos-config. Maybe a
> libgeos-dev-common package would help? Any advice appreciated.
> 
> Steve
> 
> 
> _______________________________________________
> Pkg-grass-general mailing list
> Pkg-grass-general@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-general
> 



Reply to: