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>

www/p5-Parse-HTTP-UserAgent: Add LICENSE_FILE

Remove # $FreeBSD$ from Makefiles.

Fix every instance of RUN_DEPENDS:=${BUILD_DEPENDS} in p5 ports, except
for where it resulted in a change in output from build-depends-list or
run-depends-list.

Approved by:	portmgr (adamw)

Update WWW

search.cpan.org is shutting down.
It will redirect to metacpan.org after June 25, 2018.

With hat:	perl

Update to 0.42

Changes:	http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes

Fix license information for portgs that use "the same license as Perl".

Sponsored by:	Absolight

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

With hat:	portmgr
Sponsored by:	Absolight

- Add NO_ARCH

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

- Fix PORTSCOUT

- Fix PORTSCOUT

- Add PORTSCOUT: reject developer releases

- Update to 0.39

Changes:	http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes

- Support STAGEDIR

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

- Update to 0.38
- Add LICENSE

Changes:	http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes

- Cleanup Makefile header

- Convert to new perl framework

- Update to 0.35

Changes:        http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes

- Update to 0.34
- Add TEST_DEPENDS

Changes:        http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
Feature safe:   yes

- Update to 0.33

Changes:        http://search.cpan.org/dist/Parse-HTTP-UserAgent/Changes
Feature safe:   yes

- Add p5-Parse-HTTP-UserAgent 0.32

Parse::HTTP::UserAgent implements a rules-based parser and tries to identify
MSIE, FireFox, Opera, Safari & Chrome first. It then tries to identify Mozilla,
Netscape, Robots and the rest will be tried with a generic parser. There is also
a structure dumper, useful for debugging.

User agent strings are a complete mess since there is no standard format for
them. They can be in various formats and can include more or less information
depending on the vendor's (or the user's) choice. Also, it is not dependable
since it is some arbitrary identification string. Any user agent can fake
another. So, why deal with such a useless mess? You may want to see the choice
of your visitors and can get some reliable data (even if some are fake) and
generate some nice charts out of them or just want to send an HttpOnly cookie if
the user agent seems to support it (and send a normal one if this is not the
case). However, browser sniffing for client-side coding is considered a bad
habit.

WWW: http://search.cpan.org/dist/Parse-HTTP-UserAgent/

Feature safe:   yes