mirror of
https://github.com/facebook/sapling.git
synced 2024-10-12 17:58:27 +03:00
36c4ce233d
Summary: On Windows `%include` can have paths containing environment variables like `%PROGRAMDATA%`. We already ship that kind of config files to users therefore let's add support for that. The change assumes `%` is not used as part of a normal path, which is probably good enough for practical uses. If `%` does need to be legally used in a filename, we can add escaping support later. Reviewed By: DurhamG Differential Revision: D9283303 fbshipit-source-id: bcc80307fe19dfc40aea88b6a0a5f69681e835fc |
||
|---|---|---|
| .. | ||
| argparse | ||
| cdatapack | ||
| clib | ||
| commitcloudsubscriber | ||
| configparser | ||
| hg_watchman_client | ||
| indexedlog | ||
| linelog | ||
| lz4-pyframe | ||
| minibench | ||
| mpatch | ||
| mpatch-sys | ||
| pathencoding | ||
| pathmatcher | ||
| radixbuf | ||
| revisionstore | ||
| third-party | ||
| treestate | ||
| vlqencoding | ||
| watchman_client | ||
| zstdelta | ||
| Cargo.toml | ||
| README.md | ||
lib
Any native code (C/C++/Rust) that Mercurial (either core or extensions)
depends on should go here. Python code, or native code that depends on
Python code (e.g. #include <Python.h> or use cpython) is disallowed.
As we start to convert more of Mercurial into Rust, and write new paths entrirely in native code, we'll want to limit our dependency on Python, which is why this barrier exists.
See also hgext/extlib/README.md, mercurial/cext/README.mb.
How do I choose between lib and extlib (and cext)?
If your code is native and doesn't depend on Python (awesome!), it goes here.
Otherwise, put it in hgext/extlib (if it's only used by extensions) or
mercurial/cext (if it's used by extensions or core).