Release source tarballs lack a top-level directory #1894

The release source tarballs (e.g. VeraCrypt_1.26.29_Source.tar.bz2) extract their contents directly into the current directory (contrib/, doc/, src/, ...) instead of into a single top-level directory such as VeraCrypt_1.26.29/.

Most distribution build systems expect a tarball to unpack into one directory named after the project and version. Without it, packagers have to override the unpack step. This came up in the OpenWrt package review: openwrt/packages#30597 (comment)

Could future release tarballs contain a top-level directory? git archive --prefix=VeraCrypt_$VERSION/ ... (or tar --transform) would do it. For reference, the GitHub tag archive for VeraCrypt_1.26.29 already has a top-level directory and the same 1706 files as the release tarball.