atoi('') (ex: RT and Horde). While I'm here, de-"pkg-comment"-ify. Port
revision bump.
Submitted by: Larry Rosenman <ler@lerctr.org>
Approved by: maintainer
queues and shutting down the database. Not bumping port revision, but if
you are having problems related to the above, update as necessary.
Submitted by: Larry Rosenman <ler@lerctr.org>
Fixes numerous bugs especially with various interface libraries and
pg_dump. All users are advised to upgrade. This update fixes all known
problems with the postgresql7 port. See release notes for details:
http://developer.postgresql.org/docs/postgres/release-7-3-2.html
A dump/restore is *not* required when upgrading to this version.
PR: ports/47983 [1], ports/47284 [2], ports/47808 [3]
Submitted by: maintainer [1]
Jason C. Wells [2]
Michel Oosterhof <m.oosterhof@xs4all.nl> [3]
* The compiler in -CURRENT now complains if you precede -I/usr/include
with -I... . The same applies to -I/usr/lib .
* The distribution's configure file treats the compiler's unexpected
warning message as a failure and errors out.
Maintainer notified in private mail.
A note about how to install languages into a PostgreSQL database is added.
PR: ports/29916
Submitted by: Palle Girgensohn <girgen@partitur.se> (MAINTAINER)
Michal Pasternak <doc@lublin.t1.pl> (the note)
* Pass the -s option to pg_ctl, to avoid clobbering the display.
It will show error messages only.
* Echo the port name after shutdown.
No functional changes, no PORTREVISION.
* Move the call to configure.postgresql7 from pre-fetch to pre-extract, so it
won't hang while performing batch fetch operations (like portupgrade -F)
* Add some TCL related files to pkg-plist.tcl, and add a PLIST_SUB in the
Makefile to register the correct tcl version in the plist.
* Do not start postgresql if the database directory does not exist: the
startup sequence could hang because of this.
* Use the "-s" option when starting postgresql with pg_ctl, so it won't
display informational messages. Display only the port name, as do other
packages startup scripts.
Approved by: Palle Girgensohn <girgen@partitur.se>
This would cure headache like apache module linking against libpq
fail to work after rebooting.
Originally, maintainer and I want this commit to go with the
PostgreSQL updating. But we both think that the latest PostgreSQL
would not be released before FreeBSD 4.3-RELEASE ports freeze.
As a conclusion, PORTREVISION bumped.
Discussed with/Submitted by: MAINTAINER
- pkg-install used wrong uid#
- chown lib dir *after* it is created
- pkg-install created data dir where Makefile didn't
- add pkg-deinstall and remove user & group
- don't chown data dir, since we don't create it anymore
- spell and documentation fixes in the rc.d script
PR: ports/25817
Submitted by: MAINTAINER
The DB is 64-bit capable so really only a few
bits of configuration for FreeBSD were needed.
Submitted by: Thomas Valentino Crimi <tcrimi+@andrew.cmu.edu>
and..
<quote>
This is a really small fix:
- When compiling postgresql-jdbc, the compilation process presents a
bad path to the installed jar-file.
</quote>
PR: 13838
PR: 13865
Submitted by: Palle Girgensohn <girgen@partitur.se>
Many bugfixes and cosmetic changes
Changes by Scrappy and me
My additional changes:
- had to link libpgtcl.so with the crypt library to get rid of the
pgaccess error message, that crypt is missing
- had to add -i option in the startup script, so that pgaccess is
able to connect to the postmaster process
- removed all unnecessary patches
- updated PLIST
Thanks to the postgresql developement team, who did a great job to
simplify the postgresql port, by applying the patches and making
the autoconf mechanism more consistent.
Submitted by: The Hermit Hacker <scrappy@hub.org>
background because of the -S option.
- remove the -D datadir option, it's meaningless, because the pgsql
user environment overwrites it with the PGDATA env variable.
Since this is important and might cause some headache, I mentioned
this in ~pgsql/.profile and the startup script.
Submitted by: John Fiber
Please note: when performing a migration to 6.2 and you have an existing db,
then you have to use the *new* pg_dumpall script that comes with this new
postgresql release. The INSTALL file points this out explicitely !!!
Changes:
- startup script resides in FILESDIR
- renamed it to be in sync with INSTALL file from sources
- always install this startup script over an existing, because
of the nature of the rc.d directory I can't install it
to pgsql.sh-dist, if a pgsql.sh is already presend ...
- portlint detected trailing whitespace, usage of perl with absolute
path, usage of echo instead of ECHO and plenty things of this kind
- post installation notes updated, mentioned the mailing list
- copies the html pages as well to the share/doc directory (new manual dir)
- had to update PLIST
- shortened DESCR file, to match the 24 lines
- added post build target, that reminds the admin how to proceed when
already having a database -> INSTALL file describes migration
- updated manpages
Clean up newly imported PostgreSQL port:
- variable reorganization and cleanup
- remove NOMANCOMPRESS conditional in favour of MAN?=
- prevent import of installing user's $PATH into ${PREFIX}/pgsql/.profile
- change package name to remove 'v'
- remove some of the latent bugs left over from the postgres95 port.
