On Tue, 16 Apr 2019 21:26:17 +0200, Georges Racinet wrote: > # HG changeset patch > # User Georges Racinet <georges.raci...@octobus.net> > # Date 1555441784 -7200 > # Tue Apr 16 21:09:44 2019 +0200 > # Node ID 410396d5eca793a1b8cf9ee8ba7bce466e9be3c0 > # Parent a362b0b95e42c8f7d46d7e3a0eb4cc531fa5f2d6 > # EXP-Topic rust-crates.io > rust: published the three extension crates to crates.io
I think it's good idea to reserve the crate names, but... > --- a/rust/Cargo.toml Fri Apr 05 14:35:33 2019 +0200 > +++ b/rust/Cargo.toml Tue Apr 16 21:09:44 2019 +0200 > @@ -1,3 +1,6 @@ > [workspace] > members = ["hg-core", "hg-direct-ffi", "hg-cpython"] > exclude = ["chg", "hgcli"] > + > +[patch.crates-io] > +hg-core = {path = "hg-core"} > \ No newline at end of file Nit: ^^^^^^^^^^^^^^^^^^^^^^^^ > [dependencies] > -hg-core = { path = "../hg-core" } > -libc = '*' > +hg-core = "0.0.1" Is it worth specifying local crates by version number and patching it in place? I think the whole point of monorepo-style layout is to get rid of the complexity of the dependency management. So long as the rust hg-* crates are merely internal modules, I don't think we have to care about versioning of these crates. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel