devel/ruby-gems: Update to 3.4.2

ChangeLog:	https://github.com/rubygems/rubygems/releases/tag/v3.4.2
PR:		268578
Approved by:	meta (ruby@, maintainer)
Exp-run by:	antoine

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.

www: remove 'Created by' lines

A big Thank You to the original contributors of these ports:

  *
  *  <hvo.pm@xs4all.nl>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Dalton <aaron@daltons.ca>
  *  Aaron LI <aly@aaronly.me>
  *  Aaron Zauner <az_mail@gmx.at>
  *  Abel Chow <achow@transoft.net>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Adrian Steinmann <ast@marabu.ch>
  *  Akinori MUSHA aka knu <knu@idaemons.org>

devel/ruby-gems: Update to 3.3.7

These are fixes Ruby 3.0

Changes were compiled against all dependencies of devel/ruby-gems and
they all built cleanly.

There are five known build failures, all prexisting:

* devel/rubygem-xdg5: requires Ruby 3.0
* devel/rubygem-xdg: requires Ruby 3.1
* graphics/rubygem-objectdetect: port explicitly marked broken
* mail/rubygem-tmail: port explicitly marked broken
* science/cdcl: marked broken, unfetchable

Plus, science/rubygem-ruby-dcl gets skipped because of science/cdcl

PR:		258108
Approved by:	ruby (zi@)

www/rubygem-rails4: Update WWW

Remove # $FreeBSD$ from Makefiles.

Update to 4.2.11.3

- Take maintainership

Changes:	https://github.com/rails/rails/releases

Change RUN_DEPENDS from rubygem-sprockets-rails to
rubygem-sprockets-rails-rails4

- Bump PORTREVISION for dependency change

Clean up gemspec patch

- Add PORTSCOUT

www/rubygem-rails4: Remove bundler dependency pin on bundler < 2.0

To adapt upcoming update of sysutils/rubygem-bundler to 2.0.1.

PR:		237379
Submitted by:	meta (myself)
Reviewed by:	mfechner

Update to 4.2.11.1

Changes:	https://weblog.rubyonrails.org/2019/3/13/Rails-4-2-5-1-5-1-6-2-have-been-released/
Security:	1396a74a-4997-11e9-b5f1-83edb3f89ba1
MFH:		2019Q1

Update to 4.2.11

Changes:	https://weblog.rubyonrails.org/2018/11/27/Rails-4-2-5-0-5-1-5-2-have-been-released/

Update WWW

www/rubygem-rails4: Remove passenger option

It isn't really needed.

PR:		225428

Move textproc/rubygem-sass-rails5 to textproc/rubygem-sass-rails-rails4

- Bump PORTREVISION of dependent ports for dependency change

Fix PASSENGER_RUN_DEPENDS

dvl@ introduced the FLAVOR support to www/rubygem-passenger in r459684 which
adds PKGNAMESUFFIX.

PR:		225465
Reported by:	Daniel Ylitalo <daniel@blodan.se>

Update to 4.2.10

Changes:	https://github.com/rails/rails/commits/4-2-stable
		https://github.com/rails/rails/compare/v4.2.9...v4.2.10

Update to 4.2.9

Changes:	https://github.com/rails/rails/commits/4-2-stable
		https://github.com/rails/rails/compare/v4.2.8...v4.2.9

Move www/rubygem-jquery-rails4 to www/rubygem-jquery-rails

- Bump PORTREVISION for dependent ports

Update to 4.2.8

Changes:	https://github.com/rails/rails/commits/4-2-stable
		https://github.com/rails/rails/compare/v4.2.7.1...v4.2.8

Update RUN_DEPENDS: change from devel/rubygem-builder32 to devel/rubygem-builder

Move devel/rubygem-activejob to devel/rubygem-activejob4

- Bump PORTREVISION for dependent ports

Move devel/rubygem-actionview to devel/rubygem-actionview4

- Bump PORTREVISION for dependent ports

Update WWW: http://www.rubyonrails.org/ redirects to http://rubyonrails.org/

www/rubygem-rails4: use correct deps

Use correct versions of rubygem-coffee-rails and rubygem-web-console which
allows "rails new appname" to run without installing additional gems.

Update Rails 4 from 4.2.6 to 4.2.7.1

Security: CVE-2016-6316
Security: CVE-2016-6317

Approved by: swills (mentor)

Change all occurrences of xmj@chaot.net to johannes@perceivon.net as the owner
requested.

This only affects "Created by" lines with one exception: devel/uclcmd. There the
maintainer is changed. This was overlooked in r416918.

Approved by: junovitch (mentor)

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 v, w, x, y, and z.

With hat:	portmgr
Sponsored by:	Absolight

- Update to 4.2.6

Changes:	https://github.com/rails/rails/commits/4-2-stable
		https://github.com/rails/rails/compare/v4.2.5.2...v4.2.6

- Update to 4.2.5.2

Changes:	https://github.com/rails/rails/commits/4-2-stable
		https://github.com/rails/rails/compare/v4.2.5.1...v4.2.5.2
Security:	5a016dd0-8aa8-490e-a596-55f4cc17e4ef
MFH:		2016Q1

- Update to 4.2.5.1

Changes:	https://github.com/rails/rails/commits/4-2-stable
		https://github.com/rails/rails/compare/v4.2.5...v4.2.5.1
Security:	bb0ef21d-0e1b-461b-bc3d-9cba39948888
MFH:		2016Q1

- Update to 4.2.5

Changes:	https://github.com/rails/rails/commits/4-2-stable

- Update to 4.2.4

Changes:	https://github.com/rails/rails/commits/4-2-stable
		http://weblog.rubyonrails.org/2015/8/24/Rails-4-2-4-and-4-1-13-have-been-released/

Remove UNIQUENAME and LATEST_LINK.

UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.

Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.

Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)

Reviewed by:	antoine, bapt
Exp-run by:	antoine
Sponsored by:	Absolight
Differential Revision:	https://reviews.freebsd.org/D3336

- Update to 4.2.3

Changes:	https://github.com/rails/rails/commits/4-2-stable

- Update to 4.2.2

Changes:	https://github.com/rails/rails/commits/4-2-stable
Security:	eb8a8978-8dd5-49ce-87f4-49667b2166dd

- Sort RUN_DEPENDS

www/rubygem-rails4: update to 4.2.1

Differential Revision:	https://reviews.freebsd.org/D2710

- Add NO_ARCH

- Update RUN_DEPENDS
- Remove MONGRELCLUSTER_DESC

www/rubygem-rails4: use newer sprockets

www/rubygem-rails4: remove optional dependency on expired www/fcgi

Fix pkgname collisions

www/rubygem-rails4: create port for rails4

This port required creating a number of new ports, old versions of existing
ports and other adjustments, so do all that while here too.

Rails is a web-application framework for the MVC pattern that includes
both a template engine, controller framework, and object-relational
mapping package. Everything needed to develop web-apps that can run on
CGI, FastCGI, and mod_ruby

Being a full-stack framework means that all layers are built to work
seamlessly together. That way you Don't Repeat Yourself (DRY) and you
can use a single language from top to bottom. Everything from templates
to control flow to business logic is written in Ruby - The language of
love for industry heavy-weights.

WWW: http://www.rubyonrails.org

Submitted by:	xmj (based on)