[postgis-devel] address standardizer: core or extra?

Greg Troxel gdt at ir.bbn.com
Mon Dec 14 17:05:33 PST 2015


I just updated pkgsrc to 2.2.0.  While doing that, I noticed that the
address standardizer got built, when it hadn't before (even with my
draft 2.2.0 package).  I think this is because pcre became installed,
even though it wasn't in the dependency list.  So I forced it off to be
able to deal with the issue separately.

I have three thoughts about this:

  As a packager, I don't like things being automatically included or not
  based on dependencies.  They should be on or off, per --disable-foo,
  with some default, and if on fail noisily without the dependency.  The
  reason is to have repeatable builds that aren't influenced by the
  undocumented parts of the build environment.  I realize this is
  perhaps more difficult for users, although I'm not sure they are well
  served by optional components coming and going without noticing.

  I don't know whether to leave this forced off, or to add the required
  dependencies and insist that it be built.  I don't really want to make
  a split package to hold this.  So I wonder if this is something that
  people consider part of postgis (i.e., is postgis without it broken?),
  or is it something that a few people want but is not really core.

  Does this belong in postgis, or should it be seperate?  Or maybe
  separate but in the tarball (so that you build it from a subdir,
  assuming postgis is already installed).


Given that I've seen very little discussion on the list, I tend to think
it's not core.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 180 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20151214/f42e8f6d/attachment.sig>


More information about the postgis-devel mailing list