Unnecessary (and detrimental) directory nesting in GitHub release artifacts

[tmke8]

The .tar.gz files have this file structure:

binaryen-version_132-x86_64-linux.tar.gz
└── binaryen-version_132
    ├── bin
    ├── include
    └── lib

where they first have a directory named binaryen-version_<version> which then contains bin/, include/ and lib/. That top-most directory seems unnecessary and is actually cumbersome to deal with when using tools like bin which allow you to manage binaries downloaded from GitHub releases. Tools such as these expect a consistent path to the binary that doesn't change between versions. But for binaryen currently the path to the binary depends on the version, because the version number appears in the top-most directory name.

So it would be very helpful to me if either

• the binaryen-version_<version> directory is skipped entirely and the .tar.gz files just contain bin/, include/ and lib/ directly
• or at least the version number is removed from that directory's name

[kripken]

I think we need some directory name (to avoid the "tarbomb" issue), but isn't keeping the version number in the directory the industry norm? That is what e.g. Node.js does. It makes it easy to install multiple versions side by side.