# HG changeset patch # User Pierre Augier # Date 2024-12-18 23:27:48 # Node ID 101c1862704a5e4b098c26822aab025c188c9463 # Parent 9137b3d9da75e9d0089618e7bc5ce67a3b97c0c2 help: fix command build with rust The use of `--no-use-pep517` leads to ERROR: Disabling PEP 517 processing is invalid: project specifies a build backend of setuptools.build_meta in pyproject.toml diff --git a/mercurial/helptext/rust.txt b/mercurial/helptext/rust.txt --- a/mercurial/helptext/rust.txt +++ b/mercurial/helptext/rust.txt @@ -67,21 +67,16 @@ version to use. Using pip --------- -Users of `pip` can install the Rust extensions with the following command:: - - $ pip install mercurial \ - --global-option \ - --rust \ - --no-use-pep517 \ - --no-binary mercurial +Users of `pip` can install the Rust extensions with the following commands:: -`--no-use-pep517` is here to tell `pip` to preserve backwards compatibility with -the legacy `setup.py` system. Mercurial has not yet migrated its complex setup -to the new system, so we still need this to add compiled extensions. + $ pip cache remove mercurial + $ pip install mercurial -v \ + --config-settings --global-option=--rust \ + --no-binary mercurial --force -`--no-binary` is there to tell pip to not use the pre-compiled wheels that are -missing rust support. This might take a couple of minutes because you're -compiling everything. +`pip cache remove` and `--no-binary` are there to tell pip to not use the +pre-compiled wheels that are missing rust support. This might take a couple +of minutes because you're compiling everything. See the "Checking for Rust" section to see if the install succeeded.