`tt pack` binaries pack logic must be fixed
Open
Nobody has claimed this yet.
2sp
bug
teamE
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
- Pack tarantool enterprise executable awlays (regardless of system or bin_dir location).
- Pack tarantool 3.* executable, because it is statically linked by default.
- before 3.* non-enterprise executables must be packed only if the executable is in bin_dir of the current environment.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the tt pack command and trace its binary-selection logic for enterprise, Tarantool 3.*, and older non-enterprise executables. Check the existing packing behavior and tests, if present. Done means each executable is packed according to its system, version, enterprise status, and presence in the current environment's bin_dir.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100