pkgsrc/databases/postgresql/Makefile.common

88 lines
3 KiB
Makefile
Raw Normal View History

# $NetBSD: Makefile.common,v 1.31 2002/10/19 03:03:49 jlam Exp $
#
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
# This Makefile fragment is included by all PostgreSQL packages built from
# the main sources of the PostgreSQL distribution except jdbc-postgresql.
#
# The PostgreSQL package naming scheme, aside from the obvious piecewise
# packages, is as follows:
#
# <lang>-postgresql client-side interface to PostgreSQL
# postgresql-<lang> server-side module for PostgreSQL backend
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
DISTNAME?= postgresql-${DIST_VERS}
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
CATEGORIES+= databases
MASTER_SITES?= http://www.postgresql.org/ftpsite/source/v${DIST_VERS}/ \
ftp://ftp.postgresql.org/pub/source/v${DIST_VERS}/ \
ftp://ftp.de.postgresql.org/pub/source/v${DIST_VERS}/ \
ftp://ch.postgresql.org/mirror/postgresql/source/v${DIST_VERS}/ \
ftp://gd.tuwien.ac.at/db/www.postgresql.org/pub/source/v${DIST_VERS}/ \
ftp://looking-glass.usask.ca/pub/postgresql/source/v${DIST_VERS}/ \
ftp://ftp.sunsite.auc.dk/mirrors/postgresql/source/v${DIST_VERS}/ \
ftp://ftp.jaist.ac.jp/pub/dbms/postgres95/source/v${DIST_VERS}/
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
MAINTAINER?= jlam@netbsd.org
HOMEPAGE?= http://www.postgresql.org/
CONFLICTS+= postgresql-[0-6]* postgresql-7.0*
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
DISTINFO_FILE?= ${.CURDIR}/../../databases/postgresql/distinfo
COMMON_FILESDIR?= ${.CURDIR}/../../databases/postgresql/files
PATCHDIR?= ${.CURDIR}/../../databases/postgresql/patches
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
# Version numbering scheme:
#
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
# DIST_VERS version number on the postgresql distfile
# BASE_VERS pkgsrc-mangled version number (convert pl -> .)
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
#
DIST_VERS?= 7.2.3
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
BASE_VERS?= ${DIST_VERS}
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
BUILDLINK_DEPENDS.postgresql-lib?= postgresql-lib>=${BASE_VERS}
BUILDLINK_DEPENDS.tcl-postgresql?= tcl-postgresql>=${BASE_VERS}
USE_GMAKE= YES
GNU_CONFIGURE= YES
.include "../../mk/bsd.prefs.mk"
# PG_MB_ENCODING may be set to any of:
#
# SQL_ASCII, EUC_JP, EUC_CN, EUC_KR, EUC_TW, UNICODE, MULE_INTERNAL,
# LATIN1, LATIN2, LATIN3, LATIN4, LATIN5, KOI8, WIN, ALT
#
# This variable controls the language encoding on the backend process.
.if defined(PG_MB_ENCODING)
CONFIGURE_ARGS+= --enable-multibyte=${PG_MB_ENCODING}
.else
CONFIGURE_ARGS+= --enable-multibyte # accept default
.endif
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
CONFIGURE_ARGS+= --disable-odbc
CONFIGURE_ARGS+= --without-java
CONFIGURE_ARGS+= --without-perl
CONFIGURE_ARGS+= --without-python
CONFIGURE_ARGS+= --without-tcl
CONFIGURE_ARGS+= --without-tk
2000-12-11 17:43:11 +01:00
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
CONFIGURE_ARGS+= --includedir=${PREFIX}/include/pgsql
Update postgresql and related packages to 7.2. Thanks to Michael Graff <explorer@flame.org> for most of the work on this update. Pkgsrc changes from the previous version include removing Makefile.ssl and some patches that have been integrated into this release of PostgreSQL. We leave open the question of when to byte-compile the Python modules for the PyGreSQL interface and just do it as before, although we should consider doing the compilation as a post-install step to ensure that the timestamps are correct. We also reorder some lines in the Makefile to include Makefile.common below certain definitions (GNU_CONFIGURE, USE_BUILDLINK_ONLY) as they may possibly trigger different portions of Makefile.common. *** Please note that a dump/restore is required to migrate an existing *** *** PostgreSQL installation to 7.2. *** Major changes from version 7.1.3 are geared toward improving use in high-volume applications and include: VACUUM Vacuuming no longer locks tables, thus allowing normal user access during the vacuum. A new "VACUUM FULL" command does old-style vacuum by locking the table and shrinking the on-disk copy of the table. Transactions There is no longer a problem with installations that exceed four billion transactions. OID's OID's are now optional. Users can now create tables without OID's for cases where OID usage is excessive. Optimizer The system now computes histogram column statistics during "ANALYZE", allowing much better optimizer choices. Security A new MD5 encryption option allows more secure storage and transfer of passwords. A new Unix-domain socket authentication option is available on Linux and BSD systems. PAM authentication is also available. Statistics Administrators can use the new table access statistics module to get fine-grained information about table and index usage.
2002-04-04 09:41:00 +02:00
CONFIGURE_ARGS+= --with-htmldir=${PREFIX}/share/doc/html/postgresql
Update postgresql to 7.1.1 Pkgsrc changes include splitting into: postgresql-lib postgresql-client postgresql-server postgresql-doc with postgresql as a meta-package. Major changes from version 7.1.1 include: Write-ahead Log (WAL) - To maintain database consistency in case of an operating system crash, previous releases of PostgreSQL have forced all data modifications to disk before each transaction commit. With WAL, only one log file must be flushed to disk, greatly improving performance. If you have been using -F in previous releases to disable disk flushes, you may want to consider discontinuing its use. TOAST - Previous releases had a compiled-in row length limit, typically 8 - 32 kB. This limit made storage of long text fields difficult. With TOAST, long rows of any length can be stored with good performance. Outer Joins - We now support outer joins. The UNION/NOT IN workaround for outer joins is no longer required. We use the SQL92 outer join syntax. Function Manager - The previous C function manager did not handle NULLs properly, nor did it support 64-bit CPU's (Alpha). The new function manager does. You can continue using your old custom functions, but you may want to rewrite them in the future to use the new function manager call interface. Complex Queries - A large number of complex queries that were unsupported in previous releases now work. Many combinations of views, aggregates, UNION, LIMIT, cursors, subqueries, and inherited tables now work properly. Inherited tables are now accessed by default. Subqueries in FROM are now supported. Migration to 7.1.1 A dump/restore using pg_dump is required for those wishing to migrate data from any previous release.
2001-05-14 16:52:36 +02:00
CONFIGURE_ARGS+= --disable-readline
CONFIGURE_ARGS+= --enable-locale
CONFIGURE_ARGS+= --enable-syslog
CONFIGURE_ARGS+= --with-CXX
CONFIGURE_ARGS+= --with-template="${LOWER_OPSYS}"
post-extract:
if [ -d ${WRKSRC}/src ]; then \
${RM} -f ${WRKSRC}/src/Makefile.custom; \
${CP} -f ${COMMON_FILESDIR}/Makefile.custom \
${WRKSRC}/src/Makefile.custom; \
fi
if [ -d ${WRKSRC}/src/interfaces/libpq ]; then \
${RM} -f ${WRKSRC}/src/interfaces/libpq/GNUmakefile; \
${CP} -f ${COMMON_FILESDIR}/GNUmakefile.libpq \
${WRKSRC}/src/interfaces/libpq/GNUmakefile; \
fi