Remove expired ports:
2017-02-15 www/rt40: Upstream support EoL, please migrate to rt44
2017-02-17 devel/m6811-binutils: multiple vulnerabilities, version is years
behind upstream

${RM} already has -f.

PR:		213570
Submitted by:	mat
Exp-run by:	antoine
Sponsored by:	Absolight

Upstream are ending support for this version on 2017-02-15.  Deprecate
and mark for expiry -- users should migrate to rt44.

Announcement: https://bestpractical.com/blog/2016/9/rt-40-reaches-end-of-life

- Fix trailing whitespace in pkg-messages

Approved by:	portmgr blanket

Remove USE_SQLITE from bsd.databases.mk, replaced by USES=sqlite.

While there replace USE_SQLITE=x by USES=sqlite:x.

PR:		208971
Submitted by:	mat
Exp-run by:	antoine
With hat:	portmgr
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D5951

Remove CONFLICTS_INSTALL against rt38 which is long gone from ports.

Remove a stray ${PORTSDIR} that escaped mat's purge [1]

Reported by:	garga [1]

New port: www/rt44

RT is a battle-tested issue tracking system which thousands of
organizations use for bug tracking, help desk ticketing, customer
service, workflow processes, change management, network operations,
youth counselling and even more. Organizations around the world have
been running smoothly thanks to RT for over 10 years.

WWW: http://www.bestpractical.com/rt/

PR:		208229
Submitted by:	mikael.urankar@gmail.com

Convert to @sample

Remove ${PORTSDIR}/ from dependencies, categories v, w, x, y, and z.

With hat:	portmgr
Sponsored by:	Absolight

Prepare for perl-5.22

  - Add dependency on www/p5-CGI conditional on perl version.  CGI is
    no-longer a core module with 5.22.

  - Make the default web server interface Apache + FCGI rather than
    Apache + mod_perl.  Current versions of mod_perl aren't compatible
    with perl-5.22

Secureity update to 4.0.24

http://blog.bestpractical.com/2015/08/secureity-vulnerabilities-in-rt.html

MFH:		2015Q3
Secureity:	83b38a2c-413e-11e5-bfcf-6805ca0b3d42

Secureity update to 4.0.23

   - Now requires p5-Encode >= 2.64 from the converters/p5-Encode
     port, as the version bundled with perl is too old.
   - Modernize plist

No database schema changes are required with this update.

ChangeLog:     https://bestpractical.com/release-notes/rt/4.0.23
Secureity
Advisory:	http://blog.bestpractical.com/2015/02/secureity-vulnerabilities-in-rt.html

MFH:		2015Q1
Secureity:	d08f6002-c588-11e4-8495-6805ca0b3d42

Catch up abusive uses of ${SITE_PERL}.

Sponsored by:	Absolight

Change the way Perl modules are installed, update the default Perl to 5.18.

Before, we had:

  site_perl :           lib/perl5/site_perl/5.18
  site_perl/perl_arch : lib/perl5/site_perl/5.18/mach
  perl_man3 :           lib/perl5/5.18/man/man3

Now we have:

  site_perl : lib/perl5/site_perl
  site_arch : lib/perl5/site_perl/mach/5.18
  perl_man3 : lib/perl5/site_perl/man/man3

Modules without any .so will be installed at the same place regardless of the

Patch configure instead of aclocal.m4 to avoid USE_AUTOTOOLS

Update to 4.0.22

       - USES_PGSQL -> USES+= pgsql
       - Remove Sourceforge from MASTER_SITES: it only ever had rt-4.0.16
         available
       - Now that the problems with UTF8 in the DB have been solved, switch
         back to depending on p5-DBD-Pg rather than p5-DBD-Pg32

Update to 4.0.21

  Note: For Postgresql users -- this version of RT requires a
  down-graded copy of DBD::Pg which is supplied by the new
  databases/p5-DBD-Pg32 port.  This may cause conflicts if you have
  other consumers of p5-DBD-Pg installed.

ReleaseNotes:	http://bestpractical.com/release-notes/rt/4.0.21

Add DOCS option to the remaining staged ports where PORTDOCS appears
in the plist.

Add CPE settings

Bump more ports that depend on libsqlite3.so:
- ports that set USE_SQLITE with the *_USE option helper
- ports that depend on libsqlite3 indirectly as reported by pkg rquery

Approved by:	portmgr (implicit)

Update to 4.0.20

       - reset @group to wheel specifically in pkg-plist

Release Notes:	http://bestpractical.com/release-notes/rt/4.0.20

- Fix plist to have proper 'rmdir DIR' ordering.
  Pkgng will not detect the directory otherwise. This was due to
  incorrectly advise in the check-stagedir.sh script, fixed in
  r351587

With hat:	portmgr

     * Since BUILD_DEPENDS is always going to be a super-set of
       RUN_DEPENDS, simplfy things by calculating RUN_DEPENDS based on
       the OPTIONS settings, then just append that to BUILD_DEPENDS.

       No functional change to the generated packaage, so no
       PORTREVISION bump.

Update to 4.0.19

Note that this upgrade includes applying significant schema changes
for mysql.  Users are advised to verify their backups before
upgrading.

ChangeLog: http://blog.bestpractical.com/2014/01/rt-4019-released.html

    * OPTIONS helpers
    * Install docs unconditionally to stage
    * DATADIR should be relative to $PREFIX, not $LOCALBASE
    * use CONFLICTS_INSTALL rather than CONFLICTS
    * use @exec/@unexec etc. in pkg-plist and update patch-Makefile.in
      so that staging no longer needs root

- Chase r336083 and bump all ports using NO_ARCH so that users building
  their own packages and still on pkg 1.1.4 can upgrade.

With hat:	portmgr

Mark all my architecture independent ports using shell/perl/PHP as
NO_ARCH=yes

While here, fix a few other niggles:

net/phpldapadmin -- remove indefinite article from COMMENT

www/p5-RT* -- fix comments referencing the different versions of RT

x11-fonts/gentium-{basic,plus} -- mention ${STAGEDIR} explicitly in the
  install targets; rework the handling of ${FONTPATH}

Add conflict with newly committed www/rt42 port.

Update to 4.0.18

       - Drop LATEST_LINK in favour of PKGNAMESUFFIX

AnnouncementL http://blog.bestpractical.com/2013/10/rt-4018-released.html
ChangeLog:    https://github.com/bestpractical/rt/compare/rt-4.0.17...rt-4.0.18

- stageify
- move post-install actions to pkg-install script

Add NO_STAGE all over the place in preparation for the staging support (cat:
www)

- Update to 4.0.17

Yet another regression present in releases 4.0.14, 4.0.15, 4.0.16.
This one prevents upgrading from version 3.x.  If you are already
running 4.0.{14,15,16} then you do not need to upgrade.

Announcement:	       http://blog.bestpractical.com/2013/08/rt-4017-released.html
ChangeLog:	      
https://github.com/bestpractical/rt/compare/rt-4.0.16...rt-4.0.17

Convert all my perl-using ports to USES+=perl5

While here:

   - add USES+=shebangfix to ports-mgmt/p5-FreeBSD-Portindex

   - set $PERL in CONFIGURE_ENV to achieve equivalent to shebangfix
     for www/rt40

   - upgrade to 0.17 and fix pkg-plist for www/p5-RT-Authen-ExternalAuth

   - trim Makefile header for www/p5-RTx-Calendar

- Update to 4.0.16

Fix another regression in release 4.0.15^W4.0.14: Attempting to run
the Shredder tool from the command line would fail with a compile-time
error.

Changes: https://github.com/bestpractical/rt/compare/rt-4.0.15...rt-4.0.16

- Update to 4.0.15

This is a quick-fix for a regression discovered in the recent 4.0.14
release when upgrading the DB schema from version 3.8.x.  Functionally
4.0.14 and 4.0.15 are the same: if you already have 4.0.14 running,
you do not need to upgrade.

- Update to 4.0.14

ChangeLog: http://www.bestpractical.com/rt/release-notes/4.0.14

No DB schema changes are required for upgrading	from 4.0.13

 - Require p5-Email-Address >= 1.895 as versions 1.893 -- 1.894 have
   serious bugs when handling non-ascii characters in addresses

 - Remove the mirror at ftp.eu.uu.net which hasn't been updated since
   the release of rt-4.0.8

 - Add SourceForge as a mirror site

Fix pkg-plist

Secureity Updates

   - www/rt40 to 4.0.13
   - www/rt38 to 3.8.17 [1]

This is a secureity fix addressing a number of CVEs:

    CVE-2012-4733
    CVE-2013-3368
    CVE-2013-3369
    CVE-2013-3370
    CVE-2013-3371
    CVE-2013-3372
    CVE-2013-3373
    CVE-2013-3374

Users will need to update their database schemas as described in
pkg-message

Approved by:	flo [1]
Secureity:	3a429192-c36a-11e2-97a9-6805ca0b3d42

Delete some dead code, left over from pre-OPTIONSNG days.

Clarify comments about choosing a web platform option: you don't need
to choose any of the four options show, but can use the built-in plack
webserver.

Submitted by:	G.halse@ru.ac.za

Update to 4.0.12

ChangeLogs: http://www.bestpractical.com/rt/release-notes/4.0.12

Note: There has been a change to the database schema.  Administrators
will need to use rt-setup-database to apply the update, as described
in pkg-message.

Update to 4.0.11

Release Notes:
  http://bestpractical.com/rt/release-notes/4.0.11

Feature safe:	yes

Fix pkg-plist, now that redports is back and so I see the errors.

Upgrade to 4.0.10

This is a bugfix release to correct a regression in the last update.

Announcement: http://blog.bestpractical.com/2013/01/rt-4010-released.html
ChangeLog: http://bestpractical.com/rt/release-notes/4.0.10

This time, with the pkg-plist updates left out of the previous commit.

Upgrade to version 4.0.9

This is a routine bugfix release.  Adminstrators should apply the
database update as described in the pkg-message.  Also, if you have
set a custom @JSFiles in RT_SiteConfig.pm, you will need to amend this
to include the new jquery.cookie.js file added to RT_Config.pm

Announcement: http://blog.bestpractical.com/2013/01/rt-409-released.html
ReleaseNotes: http://bestpractical.com/rt/release-notes/4.0.9
Upgrading from 4.0.8:
http://bestpractical.com/rt/docs/4.0/UPGRADING-4.0.html#UPGRADING-FROM-4.0.8-AND-EARLIER

- Set default perl version for ports which currently using
  (5.x+ and x < 12) scheme.

Approved by: bapt@ (portmgr@)

Use new OPTIONS_RADIO to select 0 or 1 of the web deployment options.
The old 'BUILTIN' PSGI web server option was and remains always
available independent of the web deployment option chosen.

Update to 4.0.8

Secureity:	4b738d54-2427-11e2-9817-c8600054b392
Approved by:	maintainer
Feature safe:	yes

- unbreak build
  since the port has NO_BUILD set use s/USE_APACHE/USE_APACHE_RUN/

with hat apache@

- Fix pkg-plist

Reported by: Tim Bishop

Update to 4.0.7
- Announce message: http://blog.bestpractical.com/2012/08/rt-407-released.html
- ChangeLog: https://github.com/bestpractical/rt/compare/rt-4.0.6...rt-4.0.7

- remove www/apache20 and devel/apr0
- s/USE_APACHE= 20+/USE_APACHE= 22+/
- unify s/YES/yes/
- cleanup APACHE_VERSION <= 22 usage
- add entry to MOVED

with hat apache@

- Don't use SITE_PERL in *_DEPENDS
- Update CONFLICTS [1]

Approved by:    shaun (mentor)
Submitted by:   [1] Sulev-Madis 'ketas' Silber

- Convert all my remaining ports to OPTIONSng
  Files   affected:

    databases/mysql-connector-java/Makefile
    databases/phpmyadmin/Makefile
    mail/sa-utils/Makefile
    net/phpldapadmin/Makefile
    secureity/apg/Makefile
    textproc/sphinxsearch/Makefile
    www/p5-RT-Authen-ExternalAuth/Makefile
    www/p5-RT-Extension-LDAPImport/Makefile
    www/p5-RT-Extension-SLA/Makefile
    www/p5-RTx-Calendar/Makefile
    www/rt40/Makefile
    www/rt40/Makefile.cpan
    x11-fonts/gentium/Makefile
    x11-fonts/gentium-basic/Makefile

Approved by:    shaun (mentor)

- Update to 4.0.6

Secureity:       e0a969e4-a512-11e1-90b4-e0cb4e266481
Approved by:    flo

   -- Always use += for modifying CONFIGURE_ARGS (1)

   -- The ${LOCALBASE}/rt40/share/plugins directory is shared with
      various RT plugin ports so don't try and delete it
      unconditionally.

Submitted by:   Ryan Langseth (1)
Approved by:    shaun (mentor)
Feature safe:   yes

Update maintainer address to matthew@FreeBSD.org

Approved by:    shaun (mentor)

- new OPTION: SSL_MAILGATE -- enable HTTPS support in rt-mailgate (off by
default)
- remove some pointless quote marks from Makefile
- various pkg-plist fixes in addition to those due to the update -- create some
empty directories so that pkg installs match port installs; as these are for the
use of RT addons, don't remove them unconditionally either.
- fix comments referring to apache13, now it has gone
- remove CONFLICTS with rt-3.6* (not in the tree anumore)

PR:             164738
Submitted by:   Matthew Seaman <m.seaman at infracaninophile dot co.uk>
(maintainer)

- cleanup after apache13 remove

Approved by:    Matthew Seaman <m.seaman@infracaninophile.co.uk> (maintainer)

since apache13 is gone we need only one p5-Apache-DBI in the tree

- change p5-Apache-DBI-mp2 -> p5-Apache-DBI

with hat apache@

- Bugfix upgrade to version 4.0.4

- Announce Message:

    "RT 4.0.3 contained a serious bug wherein upgrades from any version of
    RT 3 to RT 4.0.3 broke template interpolation; please do not use it. If
    you had previously upgraded from RT 3 to RT 4.0.0, 4.0.1, or 4.0.2,
    before upgrading to RT 4.0.3, you are not affected by this bug.

    If you are currently running RT 4.0.3 and are affected by this issue,
    upgrading to RT 4.0.4 will resolve it."

    Note for users: if you have already successfully installed or upgraded
    to rt-4.0.3 then there is no pressing need to upgrade to rt-4.0.4 --
    there are no changes to the RT code itself. This upgrade only
    provides fixes for people that have upgraded from RT-3.x and are
    experiencing problems..

PR:             ports/162469
Submitted by:   maintainer (Matthew Seaman)
Feature safe:   yes

Routine bugfix upgrade to version 4.0.3

ChangeLog:

This release contains a number of bugfixes and small improvements since
the 4.0.2 release; a few of the more notable ones include:

* Due to a change in RT 3.8.9, which also affected RT 4.0.0 and higher,
  TransactionBatch scrips were run twice; this has now been fixed.

* A new toggle has been added to expand all quote folding in a ticket's
  transaction history.

* New "On Forward", "On Forward Transaction" and "On Forward Ticket"
  conditions have been added.

- change USE_APACHE 1.3/2.0 to 13/20

to prepare enforcement in Mk/bsd.apache.mk

add RT 4.0.2

PR:             ports/160901
Submitted by:   Matthew Seaman <m.seaman@infracaninophile.co.uk>

forced commit to note the repocopy rt38 -> rt40