sysutils/shim: Set USE_GCC=13

While we wait for expiration (or remediation), set USE_GCC=13 so that
the port does not get in the way of the GCC_DEFAULT update to GCC 14.

PR:		281248

sysutils/shim: Deprecate port

Last commit on the master branch upstream is 10 years ago.
The port does not build with GCC 14 [1].

Give 1 month for expiration date.

The port might be fixed by switching upstream to
https://github.com/rhboot/shim (actual upstream is a fork of this repo,
which is still active) and patching appropriately.
Still, I believe it makes more sense to deprecate and expire the port
since:
- apparently nobody felt the need for a more up to date version of shim;
- there are important security issues which are most likely not
addressed by the actual port
(e.g. https://github.com/advisories/GHSA-qjqj-4cq6-6f2f)

PR:		281248 [1]

*: Bump PORTREVISIONs for math/mpc update to 1.3.1

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.

sysutils: remove 'Created by' lines

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

  *  <jsmith@resonatingmedia.com>
  *  Aaron Dalton <aaron@FreeBSD.org>
  *  Aaron Landwehr <aaron@snaphat.com>
  *  Adam Weinberger <adamw@FreeBSD.org>
  *  Adrian Chadd
  *  Adrian Chadd <adrian@FreeBSD.org>
  *  Akinori MUSHA aka knu <knu@idaemons.org>
  *  Alan Eldridge <alane@FreeBSD.org>
  *  Alan Eldridge <alane@geeksrus.net>
  *  Aldis Berjoza <aldis@bsdroot.lv>
  *  Alex Deiter <alex.deiter@gmail.com>

Remove # $FreeBSD$ from Makefiles.

sysutils/shim: fix building

  * files/
    patch-lib-console.c: %s/EFI_WARN_UNKOWN_GLYPH/EFI_WARN_UNKNOWN_GLYPH/g

Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.

PR:		238330

sysutils/shim: unbreak build with GCC 9

PR:		238654
Submitted by:	tobik
Approved by:	mentors (implicit)
Obtained from:	https://github.com/rhboot/shim/pull/170

sysutils/shim: introduce new ARCH support (i386)

    Makefile
        bump PORTREVISION;
        USE_CSTD: gnu89 became gnu99 [0];

    files/
        *: if ARCH=i386, replaces ARCH with ia32;
        elf_ia32_efi.lds: sync OUTPUT_FORMAT [1];
        MokManager.c: used UINT32 for MokNum.

Reported by:	pkg-fallout
Approved by:	araujo (mentor)
Differential Revision:	https://reviews.freebsd.org/D18572

[0] shim.c:2176:3: error: this decimal constant is unsigned only in ISO C90
[1] patch-elf_x86_64_efi.lds always appended -freebsd as OUTPUT_FORMAT

Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.

This includes ports
 - with USE_GCC=yes or USE_GCC=any,
 - with USES=fortran,
 - using Mk/bsd.octave.mk which in turn features USES=fortran, and
 - with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
   c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.

PR:		231590

use @FreeBSD.org as MAINTAINER instead of my private address

  benchmarks/vegeta
  devel/busybee
  devel/git-lfs
  devel/gnu-efi
  devel/hub
  devel/libe
  devel/py-fabric3
  devel/py-fabric3
  dns/dhisd
  dns/dnscrypt-proxy2
  dns/go-geodns
  emulators/hatari
  irc/weechat-otr

sysutils/shim: update from 0.8 to 0.9

  - adopt the port;
  - original version from PR 231029 was modified;
  - add compiler, and shebangfix to USES;
  - reorder variables in Makefile (silent portlint);
  - rework do-install.

PR:		231029
Reviewed by:	fernape, mat, tcberner, trasz
Approved by:	rene (mentor)
Differential Revision:	https://reviews.freebsd.org/D17019

Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.

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

PR:		222542

Bump PORTREVISIONs of all users of math/mpc that we just updated to
version 1.1.0 (via revision 464079).

Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 under most circumstances.

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

PR:		219275

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

sysutils/shim: unbreak with gcc5 or later

In file included from /usr/local/include/efi/efi.h:35:0,
                 from shim.c:36:
/usr/local/include/efi/x86_64/efibind.h:88:24: fatal error: stdint.h: No such
file or directory

PR:		216707
Reported by:	antoine (via exp-run)

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.

Drop maintainership for some of my ports.

Remove ${PORTSDIR}/ from dependencies, categories r, s, t, and u.

With hat:	portmgr
Sponsored by:	Absolight

Update ports in the remaining categories to not use GH_COMMIT.

With minor cleanups to make things simpler.

With hat:	portmgr
Sponsored by:	Absolight

Fix BUILD_DEPENDS

For traz@ ports: Change USE_GCC=4.8+ to preferred USE_GCC=yes

Approved by:	just fix it

Install certificate and key matching what's embedded in the shim itself.

Sponsored by:	The FreeBSD Foundation

Don't hardcode "gcc48"; it would break after GCC upgrade.  Don't install
*.efi files as executables; from the strip(1) point of view they are data
files (actually, they are executables, but PE, not ELF).

Sponsored by:	The FreeBSD Foundation

New port: sysutils/shim

shim is a trivial EFI application that, when run, attempts to open and
execute another application. It will initially attempt to do this via the
standard EFI LoadImage() and StartImage() calls. If these fail (because secure
boot is enabled and the binary is not signed with an appropriate key, for
instance) it will then validate the binary against a built-in certificate. If
this succeeds and if the binary or signing key are not blacklisted then shim
will relocate and execute the binary.

Sponsored by:	The FreeBSD Foundation