* Take a stab at removing the pgsql user's home directory on deinstall.
* Only remove man/manl and others when PG_PREFIX is set.
Submitted by: maintainer
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
Do not call initdb from Makefile's post-install. Users are required to
manually run initdb, maybe after configuring their preferred database
location in pgsql's user .profile. pkg_add used to simply replace some
existing data files.
Add pkg-message to tell the user about initdb.
Remove 2 empty directories from pkg-plist (pgsql/include/port/freebsd,
pgsql/include/port), since they are not included in "make package" anyway
and cause pkg_deinstall to complain about the plist.
Remove all pgsql/data contents from pkg-plist, so "make deinstall" and
pkg_delete won't clobber existing databases. Minor version upgrades can now be
performed by means of pkg_delete and "make install", without using pg_dump.
Chown %D/pgsql/lib to root:wheel to satisfy ldconfig's recent security
requirements.
Change @dirrm of pgsql to "@unexec rmdir": pkg_deinstall won't complain if
data still exists in that directory at deinstall time.
Approved by: maintainer
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>
for building the tcl/tk based database frontend pgaccess.
For an updated version of this tool a separate port will
follow. Please test these changes well, so that we get a
nice PostgreSQL 6.2 version up and running "b4" port freeze ;-)
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
- Added missing ldconfig -m in startup file
- Modified pgsql user environment
- Make port NOPORTDOCS aware
- Add additional port docs to post-install target and updated PLIST
- recursively change owner of pgsql directory after creating .profile,
so that .profile can be modified by the pgsql user.
Hope everything is fine now.
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.
