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.

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

Remove # $FreeBSD$ from Makefiles.

www/rubygem-httpclient: update to 2.8.3

- Fix trailing whitespace in pkg-descrs, categories [p-x]*

Approved by:	portmgr blanket

- Update to 2.8.0

Changes:	https://github.com/nahi/httpclient/blob/master/CHANGELOG.md

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

- Update to 2.7.1

Changes:	https://github.com/nahi/httpclient/blob/master/CHANGELOG.md

Typos, whitespace and capitalization fixes (S-X).

Set NO_ARCH for remaining rubygem-* ports with no arch dependent files

Obtained from:  DEVELOPER_MODE
With Hat:       ruby@

Sponsored by:   RideCharge Inc / Curb

- Update to 2.6.0.1

Changes:	https://github.com/nahi/httpclient/blob/master/CHANGELOG.md

- Add LICENSE

www/rubygem-httpclient: update to 2.4.0

- Add stage support

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

- Update to 2.3.3

- Cannoicalize the WWW: [again],
- Save redirects s/http/https/ for github

- Get Rid MD5 support

- Mass fixup of WWW: lines pkg-descr based on rubygems.org Homepage meta info

Prompted by:    distilator
With Hat:       ruby@
Sponsored by:   RideCharge Inc. / TaxiMagic

RF -> RG Conversion (Part III)

With Hat:       ruby@
Tested by:      make checksum

- Re-assign all my rubygem-* ports to ruby@
  this gives us more eyes and brings us inline with perl@

  Current ruby@ members (stas, dinoex, pgollucci)
  http://wiki.freebsd.org/Ruby

Discussed with: stas on #bsdports

- Update to 2.1.5.2

- Update to 2.1.5

httpclient gives something like the functionality of libwww-perl (LWP) in Ruby.
httpclient formerly known as http-access2.

Features:

    * methods like GET/HEAD/POST/* via HTTP/1.1.
    * HTTPS(SSL), Cookies, proxy, authentication(Digest, NTLM, Basic), etc.
    * asynchronous HTTP request, streaming HTTP request.
    * by contrast with net/http in standard distribution;
          o Cookies support
          o MT-safe
          o streaming POST (POST with File/IO)
          o Digest auth
          o Negotiate/NTLM auth for WWW-Authenticate (requires net/htlm module)
          o NTLM auth for Proxy-Authenticate (requires win32/sspi module)
          o extensible with filter interface
          o you dont have to care HTTP/1.1 persistent connection (httpclient
cares instead of you)
    * Not supported now
          o Cache
          o Rather advanced HTTP/1.1 usage such as Range, deflate, etc. (of
course you can set it in header by yourself)

For more detail, see API document at dev.ctor.org/doc/httpclient/

WWW:    http://raa.ruby-lang.org/project/httpclient/

Sponsored by:   RideCharge Inc.