(5.6 has too old a version to replace and has had no security updates
since 2018 anyway)
adjust how symlinks are done to make it clearer that .jars are replaced
releases from a branch so there seems little point in keeping multiple
"new" branches, only when they make a major change that means some users
will want to stick to an older version.
update the new "main" dir to 6.4.54 which was tested by Brad.
and add information to the pkg/DESCR files explaining why one might want
to use a particular version.
5.6: the main reason to run this is if you have old Broadcom 11ac APs
5.14: last version before the network configuration section was changed,
adding complication for some vlan setups
6.0: last version supporting the popular older Atheros-based pre-11ac APs
amd some of the less popular 11ac APs
6.1: adds WPA3, but drops support for various devices and marketing takes
more control of the controller UI
https://twitter.com/superdealloc/status/1376626243865604100
used by unifi. a horrible mess but unifi doesn't work with the pure-java
code in newer versions of snappy-java (the native library is needed to
support "isValidCompressedBuffer").
only use this branch if you have one of the devices that do not work with
the unifi/stable release (Broadcom 11ac and Pico M2 flashed with unifi
firmware). Prompted by a mail from Jordan Geoghegan.
likely to fix the problem some people have seen with the C++ component
in the rebuilt version of snappy-java that we're using (this is a mess,
one of the java modules used by unifi includes C++ code which wants to
be compiled with gcc, upstream no longer provides builds for OpenBSD as
they used to do in the past. it's a wonder it works at all)
(there are newer snappy-java releases now that include a pure-java
version, but that doesn't support one of the functions that unifi uses..)
