Back
A FreeBSD port of RT version 4
RT (Request Tracker)
is an industrial grade ticketing system used by organisations large
and small around the world; many of them household names.
There new RT
4.0.2 port has now been committed, and the old RT 3.6.x port
has expired and been removed. For
now, RT 3.8.x is
still available, but I would encourage people to upgrade. There's
just too
much interesting
new stuff to ignore.
New stuff in the Port
- Support for several web deployment options:
- apache + mod_perl
- apache + mod_fastcgi
- lighttpd + mod_fastcgi
- Stand-alone spawn_fcgi server (eg. use with nginx)
- New dependency
on jsmin for
high performance minifying of Javascript.
What's done
- Created port for rt40 based on the existing rt38 port. This
passes the basic tests of installing and deinstalling
cleanly, and passes RT's built-in tests.
- Submitted PR ports/16091 for new www/rt40 port
- Port was committed with minor changes, amongst which was
dropping support for apache-1.3.x (due to expire on
2011-11-01).
- Committed PRs — Deprecate and Expire RT plugins not
compatible with 3.8.x or later:
www/p5-RTx-Shredder (ports/160904),
www/p5-RTx-RightsMatrix (ports/160905),
www/p5-RTx-Statistics (ports/160903)
- Submitted PR to update
www/p5-RT-Authen-ExternalAuth (ports/160953) adding RT 4.0.x compatibility and dropping
support for RT 3.6.x (Committed)
- Submitted PR to update
www/p5-RT-Extension-LDAPImport (ports/160954) adding RT 4.0.x compatibility and dropping
support for RT 3.6.x (Committed)
- Submitted PR to update
www/p5-RT-Extension-SLA (ports/160955) updating to version 0.05, adding RT 4.0.x
compatibility and dropping support for RT 3.6.x (Committed)
- Submitted PR to update
www/p5-RTx-Calendar (ports/160976) adding RT 4.0.x compatibility, adding
required code patched obtained
from github
and dropping support for RT 3.6.x (Committted)
- Updated port to RT
4.0.3 (ports/162420) (Committed). This update was very quickly
superceeded by RT 4.0.4 as it had deficiencies in the data used
to update database schema. If you've already installed 4.0.3
and everything is working fine, then there should be no great
urgency to upgrade to 4.0.4 as that is functionally identical.
On the other hand, if your ticket database schema didn't update
smoothly, then you should try 4.0.4 straight away.
- Updated port to RT
4.0.4 (ports/162469) (Committed)
- Update port to RT
4.0.5 (ports/164738) (Committed). Incremental bug-fix and
updates to RT functionality. Similar evolutionary changes to
the port. No DB schema changes over 4.0.2.
- Update port to RT 4.0.6 (Committed). This is an important
update fixing a large number of security problems which everyone
should apply as soon as possible. See the
FreeBSD VuXML entry or Best
Practical's announcement for details. There is a small DB schema to be
applied if you are using MySQL as your RDBMS.
To do
- Testing. There are 4 web deployment options and 4 database
options — as many as possible of the combinations should
be tried. I'd be very glad to receive reports from anyone
deploying RT 4.0.x about how well the various combinations
work.
- Ditto there are 4 different perl versions currently
available in ports. All my testing has been with lang/perl5.12:
needs exposure to the others.
- Development mode: need to port several perl test modules for
proper support. This should utilize the
new TEST_DEPENDS framework.
- Reimplement the port using
the OptionsNG framework, once that is committed. OptionsNG
will abstract a lot of the "choose one from these, and one from
those" logic.