Commit graph

5 commits

Author SHA1 Message Date
tonnerre
694bbd4154 Update rt3 to version 3.8.1 (from 3.6.6). Changes are:
* New visual style (web2).
 * Rich text mails.
 * Email signatures and encryption.
 * User settings for:
   - Ticket history ordering.
   - Timezones.
   - Date and time format.
   - Username format.
   - Default queue.
   - Size of message text boxes.
 * Charts of ticket relationships.
 * Breeze through upgrades with new upgrade tools.
 * Subscribe to iCalendar feeds of ticket due dates.
 * Bookmark frequently-used tickets.
 * Turn off mail from RT when you go on vacation.
 * Get your mail from RT as a daily or weekly batch.
 * Delete historical or spam tickets with RT::Shredder (only as a superuser).
 * Set up more configurable business rules with new Scrip Conditions and
   Actions.
 * Forward tickets to third-parties from within RT.
 * Enable and Disable RT extensions with the new Plugins system.
 * Automatically log out inactive users with rt-clean-sessions.
 * Run faster with less memory, thanks to numerous  performance improvements
   and bug fixes.
 * Fixed a potential HTML injection attck via user's properties.
 * Better support for installation on Solaris and FreeBSD (non-GNU make).
 * Updates to documentation and scripts for upgrading from MySQL 4.0
 * Updated upgrade documentation for the new Queue Tag and bookmarks features.
 * Multiple bugs in iCal support fixed.
 * Backwards compatibility fixes for extensions developed against 3.6
 * Added support for external links in tabs and targets.
 * Addition of a new callback before ticket creation so you can implement
   custom validation or stop creation for another reason.
 * Missing documentation to external authentication configuration variable
   in bin/rt and make it possible to set it via ENV.
 * Merged method in RT::Ticket.
2008-08-23 23:58:29 +00:00
jlam
4390d56940 Make it easier to build and install packages "unprivileged", where
the owner of all installed files is a non-root user.  This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.

(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
    unprivileged.mk.  These two variables are lists of other bmake
    variables that define package-specific users and groups.  Packages
    that have user-settable variables for users and groups, e.g. apache
    and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
    etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
    so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
    and ${UNPRIVILEGED_GROUP}.

(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.
2007-07-04 20:54:31 +00:00
rillig
bdba6495e7 Made the dependency to SpeedyCGI optional, disabled by default. Bumped
PKGREVISION.
2006-10-01 18:44:57 +00:00
cube
2ec97b6708 Update rt3 to version 3.4.5. This is _not_ an easy update, although the
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.
2006-05-01 09:38:08 +00:00
cube
d67f205365 o Rename Makefile.options into options.mk for consistency with all other
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.
2005-09-08 13:43:05 +00:00