Big thank you to Florian Walpen <dev@submerge.ch> and
Goran Mekić <meka@tilda.center> for working on Jack2.
PR: 251125
Submitted by: Florian Walpen <dev@submerge.ch> (original version)
The new version uses Java 8.
Drop maintainance: it's low effort but I am using this less now.
Reported by: portscout
Approved by: thierry (mentor, implicit)
The upcoming OpenLDAP 2.5 update requires a format change to mdb
databases. It is mandatory for existing slapd-mdb(5) databases to
be exported via an OpenLDAP 2.4 slapcat prior to upgrade, then
reloaded via an OpenLDAP 2.5 slapadd after upgrade.
To make sure that the user always have a backup somewhere, introduce
a backup mechanism (enabled by default, and may be disabled by setting
rc.conf variable slapd_autobackup_enable to "NO") in the slapd rc.d
script upon shutdown.
By default, the backups will be stored at /var/backups/openldap and
a total of 8 backups will be kept, with the oldest backup overwritten
as needed. Backups are compressed using zstd, or, when zstd is not
available, using gzip. The compression can be disabled by setting
slapd_autobackup_compress to "NO", if desirable (e.g. if /var/backups
is located on a file system that is capable of doing compression,
like ZFS).
keyd has several unique features many of which are traditionally only
found in custom keyboard firmware like QMK. Some of the more
interesting ones include:
- Layers.
- Key overloading (different behaviour on tap/hold).
- Per keyboard configuration.
- Instantaneous remapping (no flashing required).
- A simple and intuitive config format.
- Being display server agnostic (works on wayland and virtual console alike).
https://github.com/rvaiya/keyd
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
In the earlier net/openldap24-server commit, only those which depend on
net/openldap24-sasl-client were bumped. Bumping all dependent port that
didn't get a bump to force a rebuild of these packages.
Suggested by: kib
- Show in the configure summary if PCRE support had been disabled
- USES+=pkgconfig is required for successful configure regardless
of the selected options, without it fail with ``configure.ac:62:
error: possibly undefined macro: AC_SUBST''
- Allow to build against GNU crypt library, rather than OpenSSL,
as a crypto engine
