Description Tim Bishop 2003-06-11 16:10:15 UTC

	In it's current state the rt3 port won't compile/work with
	apache2 and mod_perl2.

Fix: This patch solves this, and a few other minor problems.

	First, apply ports/53204 to fix an issue with p5-Apache-DBI.

	The first change is the dependency list. I followed the
	dependency list given on rt's website, and updated the port.
	There's a few in the port that aren't mentioned on the rt
	site - I've dropped these in this patch and it seems to
	work. I guess the maintainer will know why they were there
	in the first place - so they might decide to keep them. I
	also added a couple of dependencies that were in the list
	on the rt website, but not in the port.

	If WITH_APACHE2 is defined I've added two DEPEND_ARGS. The
	WITHOUT_MODPERL is for the p5-HTML-Mason port which tries
	to use mod_perl (not mod_perl2), and the second is for the
	p5-Apache-DBI port. I wonder if there's a way to do this
	in the dependency list so they're tied to the right port
	only?

	To make Apache start with rt3/mason/mod_perl2 a small perl
	script needs to be run prior to the main rt3 script. This
	script is in the files directory and gets installed by the
	port. I've added a brief note about it to the pkg-message.

	Finally I've updated the pkg-plist for the above new file,
	and I've removed the RT_SiteConfig.pm file - it was rather
	annoying to see my config get destroyed by portupgrade.
	Also added the etc directory, although this makes less sense
	with RT_SiteConfig.pm remaining.

	Something I haven't patched is the way this port deals with
	setting up the database. In my opinion it's "bad" for the
	default behaviour to destroy all data during an upgrade -
	the port requires UPGRADE to be defined to preserve data.
	This could catch people out, especially now portupgrade
	makes doing multiple ports a doddle. I'd suggest changing
	this, but I'm not sure of the best approach.