setop/pyenv
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

structure, phrasing

Browse Source
This commit is contained in:
Ivan Pozdeev 2024-02-27 18:28:02 +03:00
parent 91f669c77f
commit c3f558bed8
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
plugins/python-build/README.md
View File

@ -124,17 +124,15 @@ In MacOS, Homebrew is used to find dependency packages if `brew` is found on `PA
Set `PYTHON_BUILD_SKIP_HOMEBREW` to avoid using it.
---
Homebrew is NOT used in Linux by default because it's rolling-release which causes a problem.
Upgrading a Python dependency in Homebrew to a new major version (that `brew` does without warning)
would break all Pyenv-managed installations that depend on it.
You can use a community plugin [fix-version](https://github.com/pyenv/pyenv/wiki/Plugins#community-plugins)
to fix installations in such a case.
When Homebrew is used, its `include` and `lib` paths are added to compiler search path (the latter is also set as `rpath`),
and also Python dependencies that are typically keg-only are searched for in the Homebrew installation and added individually.
**NOTE:** Homebrew is not used in Linux by default because it's rolling-release which causes a problem.
Upgrading a Python dependency in Homebrew to a new major version (that `brew` does without warning)
would break all Pyenv-managed installations that depend on it.
You can use a [community plugin `fix-version`](https://github.com/pyenv/pyenv/wiki/Plugins#community-plugins)
to fix installations in such a case.
##### Portage
In FreeBSD, if `pkg` is on PATH, Ports are searched for some dependencies that Configure is known to not search for via `pkg-config`.