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>
Start up a /usr/ports/YEAR2000 file to provide a central location for all
software. Will be buildling a nightly run shell script to pull all the Y2K
variables from ports, so that the central list remains reasonably up to date...
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
- in order to access the template1 database as pgsql user, the
environment needs the DISPLAY variable set to at least ":0"
- pgaccess loads dynamically the libpgtcl.1, some symbols from
another dynamic lib are needed as well -> libpq.so.1.0
Makefile (patch-af) modified (copied from the Linux clause),
so that shared lib libpgtcl is created with proper loader flags.
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.
to boot.
Have updated the Master Sites listing to reflect where the current port
actually resides, as well as added a few of the mirrors. Will work on
bringing the port up to date as I figure out how ports work :(
This should at least allow this port to be compiled using v1.08 now
