comments about meeting agenda

Greg Troxel gdt at lexort.com
Wed Jun 17 12:01:31 PDT 2026


"Regina Obe" <lr at pcorp.us> writes:

> You can't build postgis-sfcgal without building postgis too.
> It's also always assumed you want to build postgis, unless you build --without-pgconfig.
> When you use that --without-pgconfig it only builds the tools shp2pgsql /shp2pgsql / raster2pgsql

For packaging, things that belong in separate packages should be
separable.  I'm fine with core things being declared core and not
separated.  If things aren't that big, and they don't have an additional
dependency that is either big or hard to build, separating is just work
for no real gain.

> Then if you decided to build without next time then your
> postgis-2.5.so would not have sfcgal functions in it.
>
> That is undesirable from a PostgreSQL policy standpoint not to mention
> being confusing that the functions in the same version of postgis-2.5
> would be different.  Now with the postgis 3 series, all sfcgal
> functions are in a postgis_sfcgal-3 and postgis is in postgis-3.

Agreed.  Lots of programs have build-time tweaks, and those are not
amenable to secondary packages.  In pkgsrc we try to enable them, unless
they are too costly.  Build-time options do not play well with binary
packages.


More information about the postgis-devel mailing list