A few package-registry formats are physically formats we already handle:
.crate (crates.io) is a gzipped tarball.vsix (VS Code / Open VSX) is a zip.apk is ambiguous: Alpine packages are gzipped tarballs, Android packages are zips
Since #20, Open already falls back to git-pkgs/magic content sniffing when the extension is unrecognised, so all three open correctly today. This issue is now about making that support explicit rather than incidental: add .crate and .vsix to detectFormat so they route directly without the sniff, add tests that pin both .apk variants through the sniff fallback and .crate/.vsix through the extension path, and list all three in the README supported-formats section.
.tar.zst would be useful too but needs a zstd reader dependency; tracked separately in #23.
Wanted so git-pkgs/brief can open registry artifacts directly without renaming them.
A few package-registry formats are physically formats we already handle:
.crate(crates.io) is a gzipped tarball.vsix(VS Code / Open VSX) is a zip.apkis ambiguous: Alpine packages are gzipped tarballs, Android packages are zipsSince #20,
Openalready falls back togit-pkgs/magiccontent sniffing when the extension is unrecognised, so all three open correctly today. This issue is now about making that support explicit rather than incidental: add.crateand.vsixtodetectFormatso they route directly without the sniff, add tests that pin both.apkvariants through the sniff fallback and.crate/.vsixthrough the extension path, and list all three in the README supported-formats section..tar.zstwould be useful too but needs a zstd reader dependency; tracked separately in #23.Wanted so
git-pkgs/briefcan open registry artifacts directly without renaming them.