Re: [geos-devel] NEWS comments

2018-08-21 Thread Greg Troxel
Sebastiaan Couwenberg writes: > I don't think it's the job of a packaging system to specify which > compiler features should be used for reverse dependencies. Stuff like > pkg-config was invented for that. The point is to document that a compiler capable of c++11 is required, so that if the

Re: [geos-devel] GEOS 3.7.0rc1 release

2018-08-21 Thread Greg Troxel
Sebastiaan Couwenberg writes: >> Sorry, I am not following. I dug into this harder than probably makes >> sense because I wanted to make sure there wasn't a bug in NetBSD's sed, >> in which case I would file a bug report so it is fixed. >> >> I don't see -E in POSIX's sed spec: >> >>

[geos-devel] [GEOS] #918: memory leak in GeometryCollection::getCoordinate()

2018-08-21 Thread GEOS
#918: memory leak in GeometryCollection::getCoordinate() +-- Reporter: basiliscos | Owner: geos-devel@… Type: defect | Status: new Priority: major | Milestone: Component: Default |Version: 3.6.2 Severity:

Re: [geos-devel] NEWS comments

2018-08-21 Thread Sebastiaan Couwenberg
On 8/21/18 3:38 PM, Greg Troxel wrote: > > Sebastiaan Couwenberg writes: > >> On 8/21/18 3:04 PM, Regina Obe wrote: >>> gdt said > The C++11 description is not entirely clear to me, and I think it should be extra loud up front. It's a big deal as many systems have default

Re: [geos-devel] GEOS 3.7.0rc1 release

2018-08-21 Thread Sebastiaan Couwenberg
On 8/21/18 3:26 PM, Greg Troxel wrote: > > Sebastiaan Couwenberg writes: > >> On 8/21/18 1:25 AM, Greg Troxel wrote: >>> >>> is malformed. It's the .* production that the ? applies to (present or >>> not). >>> >>> VERSION_RELEASE=`echo "$VERSION" | sed -E >>>

Re: [geos-devel] GEOS 3.7.0rc1 release

2018-08-21 Thread Greg Troxel
Sebastiaan Couwenberg writes: > On 8/21/18 1:25 AM, Greg Troxel wrote: >> >> is malformed. It's the .* production that the ? applies to (present or >> not). >> >> VERSION_RELEASE=`echo "$VERSION" | sed -E >> 's/^([0-9]+\.[0-9]+\.[0-9]+)(.*)?$/\1/'` >> >> GNU sed may be allowing this as

Re: [geos-devel] NEWS comments

2018-08-21 Thread Sebastiaan Couwenberg
On 8/21/18 3:04 PM, Regina Obe wrote: >> A few comments about NEWS: >> >> I find the style of listing the alpha and rc separately confusing for >> those who go from 3.6.2 to 3.7.0 (should be almost everyone). So >> instead of having them separate, I would start a "3.7.0 (not released >>

Re: [geos-devel] NEWS comments

2018-08-21 Thread Regina Obe
> A few comments about NEWS: > > I find the style of listing the alpha and rc separately confusing for > those who go from 3.6.2 to 3.7.0 (should be almost everyone). So > instead of having them separate, I would start a "3.7.0 (not released > yet)" section on the branch used fore 3.7

[geos-devel] NEWS comments

2018-08-21 Thread Greg Troxel
A few comments about NEWS: I find the style of listing the alpha and rc separately confusing for those who go from 3.6.2 to 3.7.0 (should be almost everyone). So instead of having them separate, I would start a "3.7.0 (not released yet)" section on the branch used fore 3.7 (which I guess

Re: [geos-devel] GEOS 3.7.0rc1 release

2018-08-21 Thread Sebastiaan Couwenberg
On 8/21/18 1:25 AM, Greg Troxel wrote: > > "Regina Obe" writes: > >> I asked Sebastian the same thing. He said it's needed in configure >> script to escape the [] as I recall. > > Of course :-) I was looking back and forth in so many rules I forgot > which it was. > > But, I figured out what

Re: [geos-devel] GEOS 3.7.0rc1 release

2018-08-21 Thread Sebastiaan Couwenberg
On 8/20/18 10:44 PM, Regina Obe wrote: > I asked Sebastian the same thing. He said it's needed in configure script to > escape the [] as I recall. Yes, see: https://trac.osgeo.org/geos/ticket/887 "The single blockquotes are stripped by m4(1), hence the need for additional quotes." > From: