summaryrefslogtreecommitdiff
path: root/mk/pgsql.buildlink3.mk
AgeCommit message (Collapse)AuthorFilesLines
2016-10-30Added postgresql96 supportadam1-3/+12
2016-10-09Bump pgsql default to 95.wiz1-2/+2
2016-02-25PostgreSQL 9.5 awarenesstnn1-3/+12
2015-10-24Unhook further PG 8.4 and 9.0 redirection.joerg1-7/+1
2015-10-24Drop EOLed PostgreSQL 8.4 and 9.0 from the supported list of PGjoerg1-2/+2
versions.
2015-01-14PostgreSQL 9.4.0:adam1-3/+12
This release adds many new features which enhance PostgreSQL's flexibility, scalability and performance for many different types of database users, including improvements to JSON support, replication and index performance.
2014-06-10Bump PostgreSQL default version to 9.3.joerg1-2/+2
2013-09-10Added databases/postgresql93 version 9.3.0adam1-3/+12
2013-04-04The PostgreSQL Global Development Group has released a security update to ↵adam1-13/+2
all current versions of the PostgreSQL database system, including versions 9.2.4, 9.1.9, 9.0.13, and 8.4.17. This update fixes a high-exposure security vulnerability in versions 9.0 and later. All users of the affected versions are strongly urged to apply the update immediately. A major security issue fixed in this release, CVE-2013-1899, makes it possible for a connection request containing a database name that begins with "-" to be crafted that can damage or destroy files within a server's data directory. Anyone with access to the port the PostgreSQL server listens on can initiate this request. Two lesser security fixes are also included in this release: CVE-2013-1900, wherein random numbers generated by contrib/pgcrypto functions may be easy for another database user to guess, and CVE-2013-1901, which mistakenly allows an unprivileged user to run commands that could interfere with in-progress backups. Finally, this release fixes two security issues with the graphical installers for Linux and Mac OS X: insecure passing of superuser passwords to a script, CVE-2013-1903 and the use of predictable filenames in /tmp CVE-2013-1902.
2012-10-05Added databases/postgresql92 version 9.2.1adam1-4/+12
2012-08-02Default to PostgreSQL 9.1 as announced on pkgsrc-users and tech-pkg two ↵asau1-2/+2
weeks ago.
2011-09-15Added databases/postgresql91 version 9.1.0adam1-3/+12
2011-05-08Adjust installed version auto-detectionadam1-13/+13
2010-10-12Remove PostgreSQL 8.2 from the list.joerg1-11/+2
2010-09-21Added databases/postgresql90 version 9.0.0adam1-3/+12
2010-02-10Change PostgreSQL default to 8.4.joerg1-2/+2
2009-08-14Unsupport PostgreSQL 8.1. Garbage collect detection of ancient versions.joerg1-32/+2
2009-07-29Added databases/postgresql84adam1-3/+12
2008-03-13Make PostgreSQL 8.2 the default version. Bump all packages using it.joerg1-3/+3
Remove PostgreSQL 8.0 as choice.
2008-03-04Added postgresql83adam1-3/+12
2007-06-06Added _VARGROUPS.rillig1-1/+6
2007-02-10Replaced the deprecated PKG_SKIP_REASON with PKG_FAIL_REASON.rillig1-2/+2
2006-12-28Change PostgreSQL default version to 8.1 and bump revision of alljoerg1-2/+2
packages which have it active by default.
2006-12-27As discussed on tech-pkg, remove PostgreSQL 7.4.joerg1-5/+2
2006-12-26Support 8.1 and 8.2 for Darwinadam1-1/+7
2006-12-09Added postgresql82 version 8.2.0adam1-3/+9
2006-10-18Added a stub describing the public interface of this file.rillig1-1/+16
2006-06-06One more reminder of PostgreSQL 7.3 to remove...joerg1-5/+2
2006-03-20postgresql81 has moved from wip to pkgsrc.uebayasi1-2/+2
2006-01-08permit postgresl81abs1-3/+9
2005-11-11Change default PostgreSQL version to 8.0.joerg1-2/+2
2005-08-06At least on NetBSD 2.0 i386 postgres80 is currently installingabs1-2/+2
lib/libecpg.so.5.0.0 not lib/libecpg.so.5.0
2005-05-24Added a variable PGSQL_VERSION that identifies the PostgreSQL version used.rillig1-1/+3
2005-05-12postgresql80-client is the correct BUILDLINK_PACKAGE word to use whenjlam1-2/+2
referring to BUILDLINK_* variables.
2005-04-11catch up with PostgreSQL 8.0.2 and support Darwin .dylibrecht1-3/+21
2005-03-24USE_BUILDLINK3 is no longer optional (and cannot be turned off). Per mailtv1-4/+2
to tech-pkg: ===== * USE_BUILDLINK3=YES will be unconditional. (In fact, USE_BUILDLINK3 will be ignored altogether by mk/; but see below.) * NO_BUILDLINK and NO_WRAPPER will be ignored by mk/. If a build happens, these phases will happen. * The existing NO_BUILD will imply the previous NO_BUILDLINK and NO_WRAPPER. If no build happens, those phases are not needed. * NO_TOOLS will be ignored by mk/. The tools phase, which provides much more than just the C compiler, will always happen regardless of package. This will make metapackage builds only slightly slower, in trade for far less user error.
2005-03-17Set PGSQL_TYPE to the PKGBASE of the PostgreSQL library package that'sjlam1-3/+7
ultimately selected. PGSQL_TYPE may be used to reference various BUILDLINK_*.${PGSQL_TYPE} variables.
2005-02-07pg80 is now in databases, not wipdan1-2/+2
2005-02-07don't recognise pg80 as pg74 alsodan1-2/+2
2005-02-01allow postgresql80 (from wip), similar to java-vm.mk and jdk14abs1-3/+8
2004-10-26Add missing PKG_SKIP_REASON when ${_PGSQL_VERSION} is defined, butxtraeme1-2/+2
the package is not postgresql "74" or "73".
2004-07-24Export the according BUILDLINK_PREFIX of postgresql-lib as PGSQL_PREFIX.recht1-1/+2
2004-07-23pgsql.buildlink3.mk is used to select a PostgreSQL version for use byrecht1-0/+74
pkgsrc. It is modeled after lang/python/pyversion.mk and like it could be influenced by user- and package-settable variables. More precisely, tt's behaviour is controlled by the following two variables: - PGSQL_VERSION_DEFAULT A user-settable variable to choose the default PostgreSQL version. Default: 74 - PGSQL_VERSIONS_ACCEPTED A package-settable list of PostgreSQL versions accepted by the package. Default: 74 73 After postgresql-* has been reimported as postgresql73* all depending packages should be changed to use mk/pgsql.buildlink3.mk.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-26 17:11:10 +0000