+-- public-package
| +- .metadata.rec
| +- public-package-0.1.tar.gz.md5
- | +- public-package-0.1.tar.gz.blake2_256
- | +- public-package-0.1.1.tar.gz.blake2_256
+ | +- public-package-0.1.tar.gz.blake2b_256
+ | +- public-package-0.1.1.tar.gz.blake2b_256
| +- public-package-0.2.tar.gz
| +- public-package-0.2.tar.gz.sha256
- | +- public-package-0.2.tar.gz.blake2_256
+ | +- public-package-0.2.tar.gz.blake2b_256
+-- private-package
| +- .internal
| +- .metadata.rec
| +- private-package-0.1.tar.gz
| +- private-package-0.1.tar.gz.sha256
- | +- private-package-0.1.tar.gz.blake2_256
+ | +- private-package-0.1.tar.gz.blake2b_256
|...
@end verbatim
existent directory contents (you are downloading package you have not
seen before), then GoCheese will download information about package's
versions with checksums and write them in corresponding
-@file{.sha256}, @file{.blake2_256}, @file{.sha512}, @file{.md5} files.
+@file{.sha256}, @file{.blake2b_256}, @file{.sha512}, @file{.md5} files.
However no package package tarball is downloaded.
If JSON API is enabled, then metadata is also downloaded and stored in