mirror of
https://github.com/pyenv/pyenv.git
synced 2026-09-10 15:46:17 -04:00
094c0a80ed
Packaging a version by hand means running `pyenv install`, `pyenv binary save` and `pyenv binary generate-installer` in turn and keeping the names they produce in step. `build` runs the three in one pass, so the archive, its metadata and the definition all come out named after the entry. * The entry name is given explicitly as `<version>:<entry>`, reusing the syntax `pyenv install` already accepts, so a packaged build can sit beside a plain source install of the same version * Entry names that `pyenv install` would not install under (`latest`), or that would point outside versions/, are refused before anything is compiled rather than after * Linux only for now, matching `save` and `generate-installer` |
||
|---|---|---|
| .. | ||
| build.bats | ||
| generate-installer.bats | ||
| relocate.bats | ||
| save.bats | ||
| test_helper.bash | ||