PostGIS 3.7.0rc2 released
Greg Troxel
gdt at lexort.com
Tue Sep 8 17:30:31 PDT 2026
I think I understand better now.
* details
rsvg-convert is listed as needed, but configure.ac doesn't look for it.
It does look for convert, but doesn't check that it does what you need -
I'm unclear on if a working convert always does, or if it's optional.
* big picture
Within the "make docs" top-level target there are a lot of subsidiary
docs targets. Some of them fall into "things a package ought to have
installed", and some seem more obscure. In packaging, what I want is a
way to ask for the things that belong in a package. If visual examples
require things that aren't compatible with packaging build
environments, I'm ok with having those be off.
Looking in doc/Makefile I see
ifeq ($(CAN_BUILD_COMMENTS),yes)
BUILD_TARGET += comments
endif
ifeq ($(CAN_BUILD_PDF),yes)
BUILD_TARGET += pdf
endif
ifeq ($(CAN_BUILD_EPUB),yes)
BUILD_TARGET += epub
endif
but I see no such if for visual examples. Perhaps that's the problem,
or perhaps there should be split targets from top-level, or make docs
removed and documented which targets should be called, for things to be
"make installed".
I admit to not paying attention to doc details; for years things have
built and the binary package has man pages. (I don't want to depend on
latex.)
More information about the postgis-users
mailing list