A question on deployment please.
I need the ability to repeatedly deploy Postgresql to target SUSE Linux platforms that won't have a compiler.
I don't want to use pre-built RPMs as may need to tailor what's delivered.
So, having the source on an internal SUSE Linux build server, building there, and using that build as a start point for a deployment package seems the way to go.
Aside from creating users and some configuration on the target platform, it seems that a copy of /usr/local/pqsql is all that actually needs to be deployed. But this would build into my deployment method knowledge of how Postgresql works under the hood (i.e. what needs to be deployed). A better method would be to build "proper" RPMs from the source using rules that come with the release.
This document (http://wiki.postgresql.org/wiki/RPM_Installation) suggests that if I download a source RPM I can do an "rpm --rebuild" from the "rpm build area". This sounds good as I'd expect to then get correct binaries and RPMs to deploy them. But I can only find a source tar and not a source RPM.
So, my questions:
Is simply packaging /usr/local/pqsql (or alternative) reasonable?
If source RPM is the way to go, where can I find a source RPM?
If not, what's the best way to produce a deployment package from source using rules defined by the release?
pgsql-novice by date
|Next:||From: Devrim GÜNDÜZ||Date: 2012-01-25 12:57:59|
|Subject: Re: generating deployment pkge from source|
|Previous:||From: Michael Wood||Date: 2012-01-21 19:49:17|
|Subject: Re: How to build a query|