Skip to content

(fix) Find the binary inside a release archive's wrapper directory - #102

Open
SAY-5 wants to merge 1 commit into
HMythical:rootdevfrom
SAY-5:fix/nested-binary-lookup
Open

SAY-5 wants to merge 1 commit into
HMythical:rootdevfrom
SAY-5:fix/nested-binary-lookup

Conversation

@SAY-5

@SAY-5 SAY-5 commented Nov 13, 2026

Copy link
Copy Markdown

Description

find_binary_in_dir only searched the top level of the extract directory, so release archives that wrap everything in one versioned directory (hexyl-v0.17.0-x86_64-unknown-linux-gnu/hexyl, ripgrep-15.2.0-x86_64-unknown-linux-musl/rg) never had their binary found. When the extract directory holds nothing but a single directory, the lookup now runs again inside it. The new test uses the layout from the issue and fails without the change.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update
  • Refactoring
  • Test addition

Platform

  • Linux
  • Windows
  • Both

Testing

  • All existing tests pass
  • New tests added (if applicable)
  • Tested on macOS (cargo test, cargo fmt --check, cargo clippy --all-targets -- -D warnings, with the linux cfg gates widened to unix locally since the crate does not build there otherwise; Linux and Windows left to CI)

Checklist

  • Code follows project conventions
  • Self-reviewed code
  • Documentation updated
  • No new warnings
  • Changes limited to one platform (if applicable)
  • Commit messages follow project style

Related Issues

Closes #34

Screenshots/Videos

Signed-off-by: Sai Asish Y <say.apm35@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

build/draft pick an uninstallable GitHub release asset, and miss binaries nested inside archives (reported as success)

1 participant