Commit cb1c3c24 authored by Christoph Berg's avatar Christoph Berg

pg_buildext: Document the loop action (present since version 141).

parent 1f28c8d1
......@@ -9,6 +9,7 @@ postgresql-common (153) UNRELEASED; urgency=medium
* postgresql-common.postinst: Call su without - to avoid a warning.
* t/003_package_checks.t: Add test case for logrotate.
* t/020_create_sql_remove.t: Make pipe writes unbuffered.
* pg_buildext: Document the loop action (present since version 141).
[ Martin Pitt ]
* testsuite, pg_virtualenv: Don't fail if ifconfig is not installed. We
......
......@@ -4,7 +4,7 @@
# versions
#
# (C) 2010 Dimitri Fontaine <dfontaine@hi-media.com>
# (C) 2011-2013 Christoph Berg <myon@debian.org>
# (C) 2011-2014 Christoph Berg <myon@debian.org>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
......@@ -125,7 +125,7 @@ do
;;
configure|build|install|clean|loop)
[ "$target" ] || die "syntax: pg_buildext $action <srcdir> <target> ..."
[ "$target" ] || die "syntax: pg_buildext $action [...]"
# be verbose?
$action $v
;;
......
......@@ -4,56 +4,58 @@ pg_buildext - Build and install a PostgreSQL extension
=head1 SYNOPSIS
B<pg_buildext> I<action> I<target> I<opts>
B<pg_buildext> I<action> [I<options>]
=head1 DESCRIPTION
B<pg_buildext> is a script that will build a PostgreSQL extension in a C<VPATH>
way. It supports the B<configure>, B<build>, B<install>, and B<clean> actions,
and will choose to build for the intersection of versions known in
way, for potentially several PostgreSQL server versions in parallel.
It builds for the intersection of versions known in
C<debian/pgversions> (versions supported by the package) and in
C</usr/share/postgresql-common/supported-versions> (versions supported in this
release).
=head1 OPTIONS
=head1 ACTIONS
=over 4
=item B<action>
One of B<configure>, B<build>, B<install>, or B<clean>.
=item B<target>
Most actions expect a directory name where to build the sources. It will get
created for you if it does not exist. If the I<build-dir> contains a C<%v>
sign, it will get replaced by the specific version of PostgreSQL being built
against. (Usually this parameter is C<build-%v>.)
The target directory where to build the sources, it will get created for you
if it does not exist. If the B<target> contains a C<%v> sign, it will get
replaced by the specific version of PostgreSQL being built against.
(Usually C<build-%v>.)
=over 4
=item B<opts>
=item B<supported-versions>
C<%v> signs in B<opts> will get replaced as in B<target>.
Print effective list of supported versions, i.e. the intersection of the sets
of versions supported by the system and the package.
=over 4
=item B<configure> I<build-dir> [I<extra-configure-options>]
=item B<configure>
For every supported version, call B<../configure> from the I<build-dir>
directory. (Most PostgreSQL extensions do not have a configure script.)
Options to pass to the I<configure> script. (Most PostgreSQL extensions do not
have a configure script.)
=item B<build> I<build-dir> [I<extra-cflags>]
=item B<build>
Build the extension in the I<build-dir> directory.
Custom C<CFLAGS> options to use for the build.
=item B<install> I<build-dir> I<package-pattern>
=item B<install>
Invoke B<make install> from the I<build-dir> directory.
The third parameter specifies the package name to use. Most packages
use B<postgresql-%v-pkgname>. Make will be
called with DESTDIR="$(CURDIR)/debian/I<package>".
Package name to install for. Make will be called with DESTDIR="$(CURDIR)/debian/I<package>".
=item B<clean> I<build-dir>
=item B<clean>
Clean the build directory.
B<clean> does not take extra options.
=item B<loop> I<package-pattern>
=back
As a variant to calling B<build> and B<install> separately for VPATH builds,
loop over the supported PostgreSQL versions in the top source directory. This
should be used if the package does not support VPATH builds. As it also invokes
B<make install>, it should be placed were installation happens in debian/rules,
rather than where build would normally be called.
=back
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment