[#87] Use statically linked binaries for linux

[chshersh]

Resolves #87

[chshersh]

I checked that the binary is indeed statically linked:

~/Downloads/tool-x86_64-unknown-linux-musl$ ldd tool 
	statically linked

~/Downloads/tool-x86_64-unknown-linux-gnu$ ldd tool
	linux-vdso.so.1 (0x00007fffb8469000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fd588bfe000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd588bdb000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fd588a8c000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd588a86000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd588894000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fd588f4e000)

[chshersh]

The release with assets is here:

• https://github.com/chshersh/tool-sync/releases/tag/untagged-70964bbee1a8be3be08a

I'll keep it for now (in case anyone wants to test it) but I'll delete it before making an actual v0.2.0 release (so don't really on it!)

[MitchellBerend]

This looks like a good change but why do we need to keep the dynamically linked one?

[chshersh]

This looks like a good change but why do we need to keep the dynamically linked one?

It's a bit awkward situation due to mutual dependency. tool-sync is hardcoded in the DB with the dynamically linked asset:

tool-sync/src/sync/db.rs

Lines 86 to 96 in 65b53bd

	"tool-sync".into(),
	ToolInfo {
	owner: "chshersh".to_string(),
	repo: "tool-sync".to_string(),
	exe_name: "tool".to_string(),
	asset_name: AssetName {
	linux: Some("x86_64-unknown-linux-gnu".to_string()),
	macos: Some("x86_64-apple-darwin".to_string()),
	windows: Some("x86_64-pc-windows-msvc".to_string()),
	},
	tag: ToolInfoTag::Latest,

And it's used in tests:

tool-sync/.github/workflows/ci.yml

Line 100 in 65b53bd

if [[ ! -x $SYNC_DIR/tool ]]; then echo "error on: tool"; false; fi

Unfortunately, GitHub API doesn't return draft releases as latest. So I can only update the test and hard-coded tool-sync info only if there's a release with musl assets.

So the easiest solution would be to just keep both of them and remove the dynamically linked asset for the v0.3.0 version after the v0.2.0 release goes live.