WRANGLING THE POSTGIS EBUILD (OR NOT)

I recently tried pumping a big fat ugly query through pgsql2shp, which resulted in a memory error. Advice from the list suggested that I upgrade beyong postgis-1.0.0, but since I installed it using an ebuild in Portage, and the most current ebuild seemed to use 1.0.0, I had to moidify the ebuild. I did so using a Portage overlay as described here, modifying the ebuild file to download 1.0.4. The didn’t work either, because apparently that ebuild was made to work with 1.1 versions in CVS, which, as of last week, were packaged with an even older version of pgsql2shp. However, NOW they come with an up-to-date pgsql2shp, as does the custom version used in the original ebuild, so I set the ebuild to dl the most recent package, and now everything works. Yay.

Also, don’t forget to run

ebuild package-version.ebuild digest

after you modify an ebuild, other wise you get ugly errors like this:

!!! Digest verification Failed:
!!! /usr/local/portage/dev-db/postgis/postgis-1.0.1_p20050805.ebuild
!!! Reason: Filesize does not match recorded size

>>> Please ensure you have sync’d properly. Please try ‘emerge sync’ and
>>> optionally examine the file(s) for corruption. A sync will fix most cases.

(Thanks, )