security/rubygem-metasploit_data_models: update to 5.0.6

Mk/**ruby.mk: Switch from USE_RUBY=yes to USES=ruby

Switch from Mk/bsd.ruby.mk to Mk/Uses/ruby.mk

Notable changes are.

- Mk/bsd.ruby.mk is moved to Mk/Uses/ruby.mk.
- USE_RUBY=yes is replaced with USES=ruby.
- USE_RUBY_EXTCONF is replaced with USES=ruby:extconf.
- USE_RUBY_RDOC is replaced with USES=ruby:rdoc.
- USE_RUBY_SETUP is replaces with USES=ruby:setup.
- RUBY_NO_BUILD_DEPENDS and RUBY_NO_RUN_DEPENDS are replaced with
  USES=ruby:{build,none,run}.
- RUBY_REQUIRE isn't used anywhere, so removed.
- USES=gem now implies USES=ruby.

This is mainly the work of yasu@ at https://reviews.freebsd.org/D27863

I have just made some cosmetic changes and ran exp-run to test that the
tree is not in a BROKEN state.

Approved by:	portmgr
Differential Revision:	https://reviews.freebsd.org/D37925

Remove WWW entries moved into port Makefiles

Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.

This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.

Approved by:		portmgr (tcberner)

Add WWW entries to port Makefiles

It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.

Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.

There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.

security/rubygem-metasploit_data_models: update to 5.0.5

security/rubygem-metasploit_data_models: update to 5.0.4

One more small cleanup, forgotten yesterday.
Reported by:	lwhsu

Remove # $FreeBSD$ from Makefiles.

Update to 4.1.1

Update to 4.0.2

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

Update to 3.0.10

Update to 3.0.8

Update to 3.0.5

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

Metasploit database requires rubygem-pg version 0.2x

PR:		228722
Reported and tested by:	Marco Beishuizen
MFH:		2018Q3

Update to 2.0.16

Update to 2.0.15

Update to 2.0.14

Update to 2.0.13

Update to 2.0.10

Update to 2.0.9

Update to 2.0.6

Update to 2.0.5

Update to 2.0.4

Update to 2.0.0

Convert USES=gem:autoplist to USES=gem since autoplist is default

create USES=gem and update rubygem- ports to use it

Note that for now ports still have to have USE_RUBY=yes to use USES=gem

PR:		209041
Differential Revision:	https://reviews.freebsd.org/D6070

Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.

With hat:	portmgr
Sponsored by:	Absolight

- Add NO_ARCH

Update security/metasploit to 4.11.2

Update:
- metasploit to 4.11.1
- rubygem-metasploit-credential to 0.13.17
- rubygem-metasploit_data_models to 0.22.6
- rubygem-meterpreter_bins to 0.0.13
- rubygem-recog to 1.0.7

Update security/metasploit to 4.10.2
Add new ports needed by this version:
security/rubygem-metasploit-concern
security/rubygem-metasploit-credential
security/rubygem-metasploit-model
security/rubygem-meterpreter_bins
security/rubygem-recog

Move back to version 0.17.0 and take maintainership, new versions do not
work with the version of metasploit currently in the tree

security/rubygem-metasploit_data_models: update to 0.20.1

PR:		193818
Submitted by:	JR Aquino <tanawts@gmail.com> (maintainer)

Revert r359770:
- it's broken, missing depends
- it doesn't work with metasploit 4.9.3 in the tree

Pointy hat:	committer and maintainer

Update to 0.17.5.

PR:		191466
Submitted by:	tanawts@gmail.com (maintainer)

Update metasploit to 4.9.2 and rubygem-metasploit_data_models to 0.17.0

PR:		ports/189046
Approved by:	maintainer timeout (2 weeks)

- Stage Safe

- Update to 0.16.4

PR:		ports/180540
Submitted by:	myself
Approved by:	maintainer timeout (tanawts@gmail.com, >5 months)

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

- Update to 0.16.1

PR:		ports/179875
Approved by:	Jr Aquino <tanawts@gmail.com> (maintainer)

- Update metasploit to 4.6.2
- Update the list of scripts
- SVN is discontinued
- new DB option for database support

PR:		ports/179159
Approved by:	maintainer timeout (15 days)