This allows the use of native SHA256 functions. From naddy@

This isn't used in got, so may as well disable from compat. From naddy@

This is now implied; the option no longer exists.

We would end up raising a spurious error when the server had no more data to send and would abort the clone operation, while everything was fine in fact. Problem reported by vazub via IRC, thanks!

For some time now, gotd was only ever available if one used the --enable-gotd flag to configure. This was fine back when gotd was still under development -- but it's now very usable, and deserves to be enabled by default.

"looks good to me" thomas

libevent doesn't need to link against libevent, but it will need its CFLAGS.

This reduces the dependency set, and syncs with got. From naddy@.

Ship the tests with the release tarballs. There's still work to do in making these tests work across the supported -portable platforms

Fix syntax for --enable-{gotd,cvg}

Make sure we include this header in the release tarball

These are looked for portably.

Include the logging functionality from gotd for the helpers.

Use the more predictable %F, aka %Y-%m-%d, instead of %G-%m-%d. %G follows the definition of ISO-8601 week-based year, which is weird. In particular, 2024 is one of such years with weird behaviour: $ date -jf %Y-%m-%d +"%F %G-%m-%d" 2024-12-30 2024-12-30 2025-12-30 Diff from Lucas Gabriel Vuotto (thanks!); stsp agrees