From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Doug Knight <dknight(at)wsi(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Capturing binary and other output destined for "make install" |
Date: | 2007-06-27 20:20:47 |
Message-ID: | 4682C69F.60409@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Doug Knight wrote:
> Is there a way within the existing installation mechanisms to capture
> the files generated by an execution of "make", compiling from source,
> that are copied to their locations during the "make install"? For
> example, I had considered executing a "make -n install", capturing that
> output, and turning it into a script. I'm not looking to make an RPM.
> I've been tasked to automate our build/install process so that we build
> once (including packages related to postgres like PostGIS, and some of
> our own applications), and install from the result of the build onto a
> number of internal servers.
make install;
make -C contrib install
tar -czvf pgsql.tar.gz /usr/local/pgsql
Sincerely,
Joshua D. Drake
>
> Thanks,
> Doug Knight
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2007-06-27 20:21:37 | Re: AutoVacuum Behaviour Question |
Previous Message | Heikki Linnakangas | 2007-06-27 20:17:21 | Re: todo: Hash index creation |