Include pagc_address_parser as part of PostGIS

[robe]

Thought about this more and since the large majority of users are PostGIS users, makes sense to just package it with PostGIS. That will minimize on all the questions about where to file bugs and since tiger uses it might allow for easier build, so people don't have to compile it on their own.

Discussed this with Steve Woodbridge and he's for the idea. That would mean we'll need to give him postgis repo access.

---

OLD THOUGHT

---

I was also thinking since we are at a stable essentially 1.0 point and the address_standardizer is now wrapped as an extension and its fairly light-weight (only extra dependencies on pcre stuff available on most Linux/Unix distros), it might be worthwhile to register it as an official PostgreSQL extension at

​http://manager.pgxn.org/

Thinking about it more, since it doesn't have any direct reliance on PostGIS, it will probably be better served if its stands on its own since it has value without anything else.

The other benefit is that folks on Unix/Linux can then install it using the pgxn client.

​http://pgxnclient.projects.pgfoundry.org/

Then I can amend the instructions accordingly to offer this simplified instruction set in PostGIS docs in additiona to hte standard svn checkout approach.

Sadly this approach doesn't work on Windows cause windows doesn't really support PostgreSQL make files unless you are building under Mingw. (strk keep your mouth shut. )

I'll be shipping address_standardizer with the newly dubbed (PostGIS bundle starting at 2.1) and update our instructions accordingly so doesn't matter for windows users.

[robe]

Done at r12716. I'm going to put in separate tickets to beef up the documentation and also break into same model we have like other extension stuff so extension portion of it lists in folder extensions.