[postgis-devel] VOTE: TWKB in PostGIS, what do you think?

[Sandro Santilli]

+1 to threat TWKB as core --strk;

On Sun, Jun 16, 2013 at 09:44:37PM -0400, Paragon Corporation wrote:
>  
> Nicklas,
> 
> If everyone is okay with just accepting your TWKB when we branch 2.2 I'm not
> even sure its worth the effort gong thru the hassle of making it an
> extension.
> 
> To me your TWKB falls in boat with raster/sfcgal (but really more with the
> other input/output functions).  While it may make sense to make it an
> extension, it makes even less sense as an extension (compared to
> raster/sfcgal) because you are not adding 
> Any additional dependencies, AND you will need to be in line with liblwgeom,
> and you've only got a couple of functions.
> 
> pgRouting doesn't even rely on compiling against any PostGIS headers and
> just uses the PostGIS public SQL api so its not a model for you unless you
> want to rewrite everything to be less efficient. 
> 
> We are as Bborie said probably a year away from releasing 2.2 at the rate
> that we move, so if you put it in 2.2. and for some reason we need to take
> it out before release, no big whoop.
> 
> +1 from me for just treating it as part of core.
> 
> Anyone else have an opinion.
> 
> Thanks,
> Regina
> 
> 
> -----Original Message-----
> From: postgis-devel-bounces at lists.osgeo.org
> [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Paul Ramsey
> Sent: Sunday, June 16, 2013 1:57 PM
> To: nicklas.aven at jordogskog.no; PostGIS Development Discussion
> Subject: Re: [postgis-devel] TWKB in PostGIS, what do you think?
> 
> On Sunday, June 16, 2013 at 10:50 AM, Nicklas Avén wrote:
> > I ask because it was mentioned earlier today that when PostGIS 
> > Schanges to cmake all dependencies also will. Is that because it is 
> > convenient or necessary?
> 
> That's a slight mis-reading. If we start building PostGIS with MSVC (driven
> by cmake) we'll have to build all the dependencies with MSVC too (driven by
> something or other). The whole point is to avoid mixing build tools over the
> entire software stack, to remove the niggly issues we've been seeing mixing
> MSVC components with Mingw components.
> 
> P