[GRASS5] GRASS5.7: pg.postgisdb path to libgis partially hard-coded

[Markus Neteler]

On Fri, Dec 05, 2003 at 05:34:44PM +0100, Moritz Lennert wrote:
> Radim Blazek said:
> > On Thursday 04 December 2003 19:05, Moritz Lennert wrote:
> >> Hello,
> >>
> >> Trying to use pg.postgisdb, I realised that part of the path to postgis
> >> is
> >> hard-coded:
> >>
> >> when I give the option '-P /usr/lib/postgresql' I get
> >>
> >> libpostgis.so.x.x dir: '/usr/lib/postgresql/lib/contrib/
> >>
> >> In the pg.postgisdb script this seems to be defined at line 176:
> >>
> >> libpostgisdir="$postgis/lib/contrib/"
> >>
> >> However, I have the postgis library installed directly in
> >> /usr/lib/postgresql/lib/ without a contrib directory. In order to use
> >> the
> >> module, I had to create a directory contrib and symlink from that
> >> directory back to the library file.
> >>
> >> Is there any reason to suppose the existance of any specific directories
> >> ?
> >
> > I have (Postgres 7.1.3):
> > ....../pgsql/lib/contrib/libpostgis.so.0.6
> > maybe the place has changed. I think that pg.postgisdb has potentialy
> > more problems, and it doesn't do anything GRASS specific except
> > '--sheep' option. Shall I remove it?
> >
> 
> I don't understand its value, yet (I was just blindly following the
> tutorial),

[that's probably no good idea :-) The tutorial is more written task oriented
 than to use top-bottom ]

> so I can't comment on that, but if you decide to keep it, it
> should not expect any specific locations.

The question is if all Linux (whatever) distros follow the same directory
layout.

Markus