Log message:
databases: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles could not be fetched (some may be only fetched
conditionally):

./databases/cstore/distinfo D6.data.ros.gz
./databases/cstore/distinfo cstore0.2.tar.gz
./databases/cstore/distinfo data4.tar.gz

Log message:
databases: Remove SHA1 distfile hashes

Log message:
all: migrate some SourceForge homepage URLs back from https to http

https://mail-index.netbsd.org/pkgsrc-changes/2020/01/18/msg205146.html

In the above commit, the homepage URLs were migrated from http to https,
assuming that SourceForge would use the same host names for both http and
https connections. This assumption was wrong. Their documentation at
https://sourceforge.net/p/forge/documentation/Custom%20VHOSTs/ states
that the https URLs use the domain sourceforge.io instead.

To make the homepages from the above commit reachable again, pkglint has
been extended to check for reachable homepages. This check is only
enabled when the --network command line option is given.

Each of the homepages that referred to https://$project.sourceforge.net
before was migrated to https://$project.sourceforge.io (27), and if that
was not reachable, to the fallback URL http://$project.sourceforge.net
(163).

Log message:
all: migrate several HOMEPAGEs to https

pkglint --only "https instead of http" -r -F

With manual adjustments afterwards since pkglint 19.4.4 fixed a few
indentations in unrelated lines.

This mainly affects projects hosted at SourceForce, as well as
freedesktop.org, CTAN and GNU.

Log message:
Extend SHA512 checksums to various files I have on my local distfile
mirror.

Log message:
Remove pkgviews: don't set PKG_INSTALLATION_TYPES in Makefiles.

Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.

Log message:
Fix DESTDIR.

Log message:
Initial import of datadraw-3.1.1

DataDraw is an ultra-fast persistent database for high performance programs
written in C.  It's so fast that many programs keep all their data in a
DataDraw database, even while being manipulated in inner loops of compute
intensive applications.  DataDraw databases are compiled, and directly link
into your C programs.  DataDraw databases are resident in memory, making data
manipulation even faster than if they were stored in native C data structures
(really).

DataDraw databases can be persistent.  Modifications to persistent data are
written to disk as they are made, which of course dramatically slows write
times.  However, DataDraw databases can also be volatile.  Volatile databases
exist only in memory, and only for the duration that your program needs it.
Volatile databases can be directly manipulated faster than C structures, since
data is better organized in memory to optimize cache performance

DataDraw supports modular design.  An application can have one or more common
persistent databases, and multiple volatile databases to support various tools'
data structures.  Classes in a tool's database can extend classes in the common
database.

DataDraw is also 64-bit optimized, allowing programs to run much faster and in
less memory than standard C programs using 64-bit pointers.  This is because
DataDraw databases supports over 4 billion objects of a given class with 32-bit
object references.