[postgis-devel] 1.3.4rc1
Greg Troxel
gdt at ir.bbn.com
Tue Oct 21 09:25:21 PDT 2008
Mark Cave-Ayland <mark.cave-ayland at siriusit.co.uk> writes:
> Greg Troxel wrote:
>> What's dragon fly? by the way I updated the README in both trunk and
>> branch. Maybe we should have an RC2?
>>
>> DragonFlyBSD is a fork of FreeBSD:
>> http://www.dragonflybsd.org/index.shtml
>>
>> I run NetBSD, but pkgsrc is also the offical packaging system for
>> DragonFly and thus people put portability patches into pkgsrc.
>
> Ummmm do we really want to start adding unsupported ports into
> PostGIS? According to the PostgreSQL repository at
> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/Makefile.shlib?rev=1.117;content-type=text%2Fplain
> dragonfly isn't even listed, and so the dragonfly PostgreSQL packages
> must be being customised by the dragonfly maintainers to add this
> extra port information. So if you are customising the PostgreSQL
> packages then I don't see why you are surprised at having to do the
> same with the PostGIS packages.
I am not surprised, just trying to reduce local patches in something I
feel responsible for.
> The good thing is that in SVN trunk, PGXS will automatically pick up
> the Makefile.shlib from PostgreSQL and so this will no longer be an
> issue moving forward.
So that means we'll need this patch for 1.3.x, but that in 1.4.x we'll
switch to PGXS? That seems entirely workable.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 193 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20081021/d53fc8f3/attachment.sig>
More information about the postgis-devel
mailing list