DAROLD Gilles wrote:
> Yes, where are the files ?
> > of this -- rpm -ql package-name gives you a complete list of files in a
> > particular rpm. The companion 'rpm -qf /some/file/some/where' gives you
Or, for laughs:
rpm -qa|grep ^postgresql|xargs -n 1 rpm -ql
This will give you a listing of a
Lamar Owen wrote:
> > The better way is to get the tarball and do a fresh compilation, you will
> > learn more about postgres (see the INSTALL file and other documentation).
> > And then all your files will go in /usr/local/pgsql by default !
>
> You know, it's responses like this that make me th
* Prasanth A. Kumar <[EMAIL PROTECTED]> [000717 08:49] wrote:
> Gilles DAROLD <[EMAIL PROTECTED]> writes:
>
> > Hi,
> >
> > Please don't use RPM if you don't want to have a Win$ based install.
> > It's remember me a very old question: Where are the DLL ?
> >
> > The better way is to get the tar
Gilles DAROLD <[EMAIL PROTECTED]> writes:
> Hi,
>
> Please don't use RPM if you don't want to have a Win$ based install.
> It's remember me a very old question: Where are the DLL ?
>
> The better way is to get the tarball and do a fresh compilation, you will
> learn more about postgres (see the
BTW, Lamar, thanks for the RPMs. Fine job.
Lamar Owen wrote:
>
> Gilles DAROLD wrote:
> > Please don't use RPM if you don't want to have a Win$ based install.
> > It's remember me a very old question: Where are the DLL ?
>
> > The better way is to get the tarball and do a fresh compilation, yo
Gilles DAROLD wrote:
> Please don't use RPM if you don't want to have a Win$ based install.
> It's remember me a very old question: Where are the DLL ?
> The better way is to get the tarball and do a fresh compilation, you will
> learn more about postgres (see the INSTALL file and other document
