33ba7d3fac
Summary: [sapling] Remove Cargo.lock on `make clean` The help text for `make clean` says: > remove files created by other targets > (except installed files or dist source tarball) So I'd expect it to remove any non-installed built state like Cargo.toml. Concretely, I was surprised by this behavior when the build failed after pulling in updates, even after running `gmake clean`. My Cargo.lock from a previous build had pinned the watchman_client crate to an old version, but the updated workingcopy crate relied on the addition of `BytesNameField` to watchman_client@main. I think it would be better if autocargo generated a Cargo.lock for us from the Buck versions of dependencies, but as long as it's being generated as a build artifact it should be removed by `make clean`. Pull Request resolved: https://github.com/facebook/sapling/pull/534 Test Plan: ``` % cd eden/scm % gmake oss % ls Cargo.lock Cargo.lock % gmake clean % ls Cargo.lock % ls: Cargo.lock: No such file or directory ``` --- Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/sapling/pull/534). * __->__ https://github.com/facebook/sapling/issues/534 Reviewed By: quark-zju Differential Revision: D43478239 Pulled By: mshroyer fbshipit-source-id: 2c472a0e1d86c85994191e242337dab8249bafaa |
||
|---|---|---|
| .github/workflows | ||
| addons | ||
| build | ||
| ci | ||
| CMake | ||
| common | ||
| configerator/structs/scm | ||
| eden | ||
| website | ||
| .gitignore | ||
| .projectid | ||
| build.bat | ||
| build.sh | ||
| CMakeLists.txt | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| make-client.py | ||
| README.md | ||
| requirements_ubuntu.txt | ||
| rustfmt.toml | ||
| SAPLING_VERSION | ||
Sapling SCM
Sapling SCM is a cross-platform, highly scalable, Git-compatible source control system.
It aims to provide both user-friendly and powerful interfaces for users, as well as extreme scalability to deal with repositories containing many millions of files and many millions of commits.
Using Sapling
To start using Sapling, see the Getting Started page for how to clone your existing Git repositories. Checkout the Overview for a peek at the various features. Coming from Git? Checkout the Git Cheat Sheet.
Sapling also comes with an Interactive Smartlog (ISL) web UI for seeing and interacting with your repository, as well as a VS Code integrated Interactive Smartlog.
The Sapling Ecosystem
Sapling SCM is comprised of three main components:
- The Sapling client: The client-side
slcommand line and web interface for users to interact with Sapling SCM. - Mononoke: A highly scalable distributed source control server. (Not yet supported publicly.)
- EdenFS: A virtual filesystem for efficiently checking out large repositories. (Not yet supported publicly.)
Sapling SCM's scalability goals are to ensure that all source control operations scale with the number of files in use by a developer, and not with the size of the repository itself. This enables fast, performant developer experiences even in massive repositories with millions of files and extremely long commit histories.
Sapling CLI
The Sapling CLI, sl, was originally based on
Mercurial, and shares various aspects of the UI
and features of Mercurial.
The CLI code can be found in the eden/scm subdirectory.
Mononoke
Mononoke is the server-side component of Sapling SCM.
While it is used in production within Meta, it currently does not build in an open source context and is not yet supported for external usage.
EdenFS
EdenFS is a virtual file system for managing Sapling checkouts.
While it is used in production within Meta, it currently does not build in an open source context and is not yet supported for external usage.
EdenFS speeds up operations in large repositories by only populating working
directory files on demand, as they are accessed. This makes operations like
checkout much faster, in exchange for a small performance hit when first
accessing new files. This is quite beneficial in large repositories where
developers often only work with a small subset of the repository at a time.
More detailed EdenFS design documentation can be found at eden/fs/docs/Overview.md.
Building the Sapling CLI
The Sapling CLI currently builds and runs on Linux, Mac, and Windows. It can be
built by running make oss in the eden/scm directory and running the
resulting sl executable.
Building the Sapling CLI requires Python 3.8, Rust, cmake, and OpenSSL for the main cli, and Node and Yarn for the ISL web UI.
License
See LICENSE.