*/*: Bump jpeg-turbo users treewide

New major version 3.0.0

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

all: Remove all other $FreeBSD keywords.

Remove # $FreeBSD$ from Makefiles.

Update WWW: SF redirects to https://sourceforge.net/projects/<PROJECT_NAME>/

Remove libjpeg.so.11 compatibility link that was added in r374303 to
prevent massive PORTREVISION bumps.  Bump dependent ports that have not
been bumped since.

Convert to USES=jpeg

Remove $FreeBSD$ from patches files everywhere.

With hat:	portmgr
Sponsored by:	Absolight

- Allow staging as a regular user
- Bump portrevision as configuration directory was not packaged

Fix build without gcc.

Support staging

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

Convert the headers of these ports I just drop maintainership of.

Paul Chvostek has graciously agreed to take maintainership of these two
ports.

Move the rc.d scripts of the form *.sh.in to *.in

Where necessary add $FreeBSD$ to the file

No PORTREVISION bump necessary because this is a no-op

In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().

In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.

- Get Rid MD5 support

Begin the process of deprecating sysutils/rc_subr by
s#. %%RC_SUBR%%#. /etc/rc.subr#

- update to jpeg-8

- Switch SourceForge ports to the new File Release System: categories starting
with N

- update to jpeg7
Tested by:      pav on pointyhat

- Remove USE_GCC where it can be satisfied with base compiler on following
  FreeBSD versions: 5.3 and up, 6.x, 7.x, 8-CURRENT

Remove bogus hunk.

Our v*printf() family of functions don't return va_list to its original
state upon return, therefore if we want to call such functions several
times on different streams we need to wrap each call to va_start/va_end
otherwise it either prints garbage on second and subsequent invocation
or simply crashes the program.

Remove USE_REINPLACE from all categories starting with N

Remove the FreeBSD KEYWORD from all rc.d scripts where it appears.
We have not checked for this KEYWORD for a long time now, so this
is a complete noop, and thus no PORTREVISION bump. Removing it at
this point is mostly for pedantic reasons, and partly to avoid
perpetuating this anachronism by copy and paste to future scripts.

Don't bogusly list the rc.d script in the plist.  USE_RC_SUBR does this
for us.

Reported by:    krismail

add SHA256

Given vncreflector a chance on 4.x.  First, require gcc-3.3 or newer as
2.95.4 appears to generate bad code (none of the debugging tools I tried
could even come up with a decent stack trace when it died.)  Second, fix
the RC script so it can find rc.subr.

Add vncreflector 1.2.4.

From the website:
    VNC Reflector is a specialized VNC server which acts as a proxy
    sitting between real VNC server (a host) and a number of VNC
    clients. It was designed to work efficiently with large number
    of clients.