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: remove 'Created by' lines

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

  *  <ports@c0decafe.net>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Ade Lovett <ade@FreeBSD.org>
  *  Aldis Berjoza <aldis@bsdroot.lv>
  *  Alex Dupre <ale@FreeBSD.org>
  *  Alex Kapranoff <kappa@rambler-co.ru>
  *  Alex Samorukov <samm@freebsd.org>
  *  Alexander Botero-Lowry <alex@foxybanana.com>
  *  Alexander Kriventsov <avk@vl.ru>
  *  Alexander Leidinger <netchild@FreeBSD.org>

Remove # $FreeBSD$ from Makefiles.

This port doesn't build for submitter with threaded make (on powerpc64).
Add MAKE_JOBS_UNSAFE=yes to fix build.

While here, pet portlint.

PR:		235528
Submitted by:	Piotr Kubaj
Approved by:	portmgr (tier-2 blanket)

Update to 0.6

Update to 0.5 [1]

While here: port related changes:
- Respect PREFIX
- Build a real shared library (with SONAME)

PR:		222483 [1]
Submitted by:	takefu@airport.fm [1]

security/bearssl: Fix build with Clang

Using MAKE_ARGS allows building with clang.

Submitted by:	bapt

security/bearssl: Fix shared library installation

While here remove useless USES=compiler

Reported by:	bapt

security/bearssl: Update to 0.4

Now requires GCC. The Clang build is not functional as it fails to link.
The cause is under investigation.

Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using using Mk/bsd.octave.mk which in turn has USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
   c++11-lang, c++0x, c11, or gcc-c++11-lib.

PR:		216707

security/bearssl: Update to 0.2

Changelog:	https://bearssl.org/changelog.html

Bump PORTREVISIONS for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).

In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.

security/bearssl: Packaging improvements

Reported by:	mat

security/bearssl: Fix build on FreeBSD 9.3

BearSSL is an implementation of the SSL/TLS protocol (RFC 5246) written
in C. It aims at offering the following features:

- Be correct and secure. In particular, insecure protocol versions and
choices of algorithms are not supported, by design; cryptographic
algorithm implementations are constant-time by default.

- Be small, both in RAM and code footprint. For instance, a minimal server
implementation may fit in about 20 kilobytes of compiled code and 25
kilobytes of RAM.

- Be highly portable. BearSSL targets not only "big" operating systems
like Linux and Windows, but also small embedded systems and even special
contexts like bootstrap code.

- Be feature-rich and extensible. SSL/TLS has many defined cipher suites
and extensions; BearSSL should implement most of them, and allow extra
algorithm implementations to be added afterwards, possibly from third
parties.

WWW: https://bearssl.org/