11:54 Kai Knoblich (kai) 

games/anki: Update to 2.1.62

* Since release 2.1.55, upstream has changed the build system to a
  homebrew solution written in Rust, which generates the files for
  ninja(1) and then uses the latter also for building.

  As a result, quite a number of patches, that revolved around the
  Bazel build system, can now be removed and the Makefile can also be
  slimmed down considerably.

  By environment variables recognized by the build system, some
  required binaries (e.g. Python, Node.js, etc.) for the build can be
  directly defined instead downloading the binary tarballs from the
  official repositories, which saving quite a bit of patches at
  the end.

  In order to be able to build Anki successfully on FreeBSD, a few
  more environment variables have been introduced via custom patches.
  With this it's possible to use an offline cache for Node.js as well
  as a native Python environment instead of a venv.

* Belatedly add devel/py-orjson as a fixed runtime dependency and
  although it's still optional in the code, the question is how long
  this will be the case.

  Thus update NOT_FOR_ARCH_REASON accordingly and keep ONLY_FOR_ARCH
  unchanged for now.

Changelogs since 2.1.54:

https://changes.ankiweb.net/changes/2.1.60-69.html
https://changes.ankiweb.net/changes/2.1.50-59.html

MFH:		No (feature release)

    5a788a6

06:16 Kai Knoblich (kai) 

games/anki: Update to 2.1.44

Since the 2.1.36 release the build system has changed significantly
again and devel/bazel is now used by upstream for the entire build
process.

With this change, a lot of bazel rules and also some translation files
needs to be downloaded from various repositories during the buildtime.

In order to still make Anki compatible with the Ports framework, the
following approach is used:

  1. Prefetch all the required files before buildtime.
  2. Create and setup a few local bazel repositories along with a set
     of custom bazel rules and to provide Node, Protobuf and Yarn from
     the Ports tree.
  3. Compile the Rust library and place the output files to the
     respective local bazel repository for further processing.
  4. Build the rest via devel/bazel

From a technical point of view, Anki should also be able to be built on
other 64-bit architectures (but requires further patching of a few bazel
rules), as soon as devel/bazel can also be built for those platforms.

The option NLS is gone because the translations are now compiled
directly into the Rust library and they only generate a small overhead.

Changelog since 2.1.35 (too many changes/fixes to list them separately):

https://changes.ankiweb.net/

Reviewed by:	tcberner
MFH:		2021Q3
Differential Revision:	https://reviews.freebsd.org/D31358

    7cb5fb3