parameter to daemonize, move the parameter from daemon to daemon_flags,
so that the user cannot inadvertently prevent it from daemonizing by
adjusting the flags.
Discussed with ajacoutot and schwarze, this method was suggested
by schwarze@ as a simpler alternative to my diff. ok aja@
jdk-1.5, and nobody noticed/complained).
- Remove MAINTAINER, because of inactivity.
kind of ok@ all those people who find it still usefull (but didn't
use it since the removal of jdk-1.5)
Two important things:
+ Fix bugs in information_schema.referential_constraints view
If you need to fix this in an existing installation, you
can (as a superuser) drop the information_schema schema then re-create it
by sourcing /usr/local/share/postgresql/information_schema.sql.
This must be repeated in each database to be fixed.
+ Make contrib/citext's upgrade script fix collations of
citext columns and indexes.
If you have a previously-upgraded database that is suffering
from this problem, and you already ran the CREATE EXTENSION command,
you can manually run (as superuser) the UPDATE commands found
at the end of /usr/local/share/postgresql/extension/citext--unpackaged--1.0.sql.
ok jeremy@
Start using MODRUBY_REGRESS with ruby, rspec2, and testrb entries.
Switch away from manual do_regress targets where possible. Add
some patches to make regress tests run for some ports.
- use /etc/rc.d to stop and start the daemon.
- use sudo rather than keep jumping between root/_postgresql users.
- use pkg_add -ui rather than just -u (allow it to ask if you've backed
up, rather than just terminating).
ok pea@
also annotate gamin for bootstrap property, and mark haddock,no_deps as
a "real flavor", since it's only used for bootstrap anyways AND significantly
changes the build.
there is a Makefile.inc.
Since the BUILD_PACKAGES tests have to happen there, put the java one there
as well, it won't trigger for db/v3, obviously.
Allows the removal of the ,java pseudo-flavor, since the ONLY_FOR_ARCH-* part
will take care of it.
