Re: Compiling to RPM setup/filesystem layout - Mailing list pgsql-general

From Steve Wolfe
Subject Re: Compiling to RPM setup/filesystem layout
Date
Msg-id 001801c0ea26$00305c00$50824e40@iboats.com
Whole thread Raw
In response to Compiling to RPM setup/filesystem layout  (Gerald Gutierrez <gml1@coldresist.com>)
List pgsql-general
> > Let's compare removing the RPM's:
>
> rpm -e `rpm -qa |grep postgresql`

  Nice.  I like it.

> > #rpm --erase php-pgsql-3.0.15-2
>
> That's not what you're doing for your manual install...
>
> > rm -rf ~postgres/*
>
> So postgres doesn't install it's binaries in /usr/local/bin, libraries
> in /usr/local/lib etc?

  I'm not sure what you mean.  When it's installed with the autoconf
defaults, the binaries go in /usr/local/pgsql/bin, and the libraries are
in /usr/local/pgsql/lib (assuming that you've chosen /usr/local/pgsql for
the base directory), and removing all traces is as easy as removing that
directory, assuming that you've followed the commonly-used practice of
having /usr/local/pgsql/data as your "data" directory.   (Yes, that should
technically go under /var.)

  Since the binaries aren't in /bin, I generally add /usr/local/pgsql/bin
to the path in /etc/profile, and /usr/local/pgsql/lib to /etc/ld.so.conf,
as described in the docs, so I suppose that to remove *every* trace,
you're right, I'd have to remove those lines as well, even though having
them around without an installation of PG isn't going to hurt much.

steve



pgsql-general by date:

Previous
From: Jeff Eckermann
Date:
Subject: RE: pg_dump & pg_dumpall problem.
Next
From: Gerald Gutierrez
Date:
Subject: Re: Compiling to RPM setup/filesystem layout