changes are apparently minor to a end user (but not for the site
administrator).
It'd very hard and very long to provide a full list of changes. The main
changes in RT 3.4 are a complete rework of how Custom Fields are handled,
which means there is a lot more flexibility in that area now (including
Custom Fields for users, per-queue, per-transaction). RT 3.4 is also
supposed to be faster, which certainly is no bad news.
Another bonus of RT 3.4 are the availability of extensions, and I will
commit RTx::Shredder and RTx::RightsMatrix very soon.
Updating RT is not an easy task, be sure to backup your database, and don't
forget to grant the new rights to relevant people.
In pkgsrc, rt3 is also seeing a few changes. The main one is the situation
of the "local" path, which is now set to /var/rt3, which seems less lame to
me than the previous value. It could be debated, though.
INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
change (it breaks for callbacks).
Inspired from the commit to solve the same issue on the 3.4 branch of RT.
Bump PKGREVISION and Mason version requirement.
packages.
o Drop the frontend- and backend- options names and replace them with
simpler ones, now that we have the PKG_OPTIONS_GROUP mechanism it's
much more easier.
o Brick me for not having done that earlier.
o Really enforce the conflicts between backend-* and frontend-* options,
as the recent changes in the options framework might confuse people in
that respect. You know have to explicitly remove the suggested options
in your PKG_OPTIONS.rt variable.
as a separate package.
The change log for that versions is as always with RT very long and
verbose. However, it is only a bug-fix release, and quite a few of them
are fixed. Among other things, a Polish translation has been added.
See the detailed information in the Changelog file at the root of the
archive.
into the bsd.options.mk framework. Instead of appending to
${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes
the default options to be the union of PKG_DEFAULT_OPTIONS and any
old USE_* and FOO_USE_* settings.
This fixes PR pkg/26590.
Collection.
This package is based on the work of Dieter Roelants in pkgsrc-wip, with
a lot of changes to make it proper WRT pkgsrc.
RT is an industrial-grade ticketing system. It lets a group of
people intelligently and efficiently manage requests submitted by
a community of users. RT is used by systems administrators, customer
support staffs, NOCs, developers and even marketing departments at
over a thousand sites around the world.
