(How to handle) Extensionless tarballs support?

[thejcannon]

👋 Howdy folks!

I'm pointing mise at an internally-hosted tool registry where some tools are uploaded as tarballs, but the URL is extentionless:

https://example.com/toolname/version

josh@computer $ file toolname-linux-amd64
toolname-linux-amd64: gzip compressed data, was "toolname-linux-amd64.tar" [...]

Unfortunately, mise seems to key off the suffix of the file/URL so no matter what I try to configure (currently trying the http backend) I just get the tarball on my PATH which unfortunately doesn't work well 😛

Is this something that's supported?

If not I'm happy to PR. Wondering what option is most appetizing:

• header-sniffing extentionless files (either by default or opt-in)
• some config/option to treat the filename as another
• some config/option to treat as tarball

[jdx]

detection might be good but really this should be configurable behavior in the config file

[jdx]

idk something like format = "tar.xz"? I haven't thought about it much though

[thejcannon]

Can I really politely ask that https://mise.jdx.dev/test-fixtures/hello-world-1.0.0.tar.gz also be exposed as https://mise.jdx.dev/test-fixtures/hello-world-1.0.0?

[jdx]

yeah I can do that

[jdx]

https://mise.jdx.dev/test-fixtures/test-fixtures_hello-world-1.0.0-tarball

[thejcannon]

Enjoy! #6957