On 03/09/2010 05:31 AM, Ben Kim wrote:
Also, how is using standard rpm, with its standard layout
(/var/lib/pgsql, /usr/lib/pgsql, ...), generally regarded? ( vs.
compiling everything ?) Does anyone think using the rpm is
unprofessional or something that only beginners will do?
I have someone who opposes the use of standard rpms (even yums) for
this reason. I thought I'd check out how it is received professionally.
I wouldn't have it any other way. (I use Ubuntu, so it's packages
instead of rpm, but it's the same.) The biggest benefit I've seen is
that the packages are built against known versions of supporting
libraries, and these libraries are also in the repository. So, an
"apt-get install postgresql" gets the latest version AND all dependencies.
Your friend sounds like a snob. :) (Though he/she may have valid
reasons for feeling that way, I haven't had that cause a problem in a
modern Linux environment. Red Hat 6? Yeah, you might want to compile -
you probably couldn't find all the dependencies anyway.)
I ask the question because sometimes I feel uneasy mixing rpms and
source compilation.
Bingo. :) When I do have to compile, I compile AND create a package
(if possible), then install the package.
Daniel
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
