Re: Problems publishing Rust crates (was: [ANNOUNCE] Git v2.49.0)

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Mar 14, 2025, 20:12 UTC
Message-ID: <Z9SNuI6hSpKEfv5A@tapette.crustytoothpaste.net>
In-Reply-To: <4zi3re4viluih7qwvwlu7mp3j6e6gjexz2bppa5am45nnqkezz@7vtwmyrfdwvi>

On 2025-03-14 at 19:43:32, Josh Steadmon wrote:

Show 12 quoted lines

> On 2025.03.14 10:16, Junio C Hamano wrote:
> >  * Foreign language interface for Rust into our code base has been added.
> 
> Unfortunately, I've run into problems publishing the new crates to
> crates.io. Specifically, the build process for `cargo publish` is
> different from `cargo build` in that the root of the repository is not
> included, and therefore our build.rs scripts cannot find the top-level
> Makefile or any of the Git sources outside of `contrib/libgit-*`.
> 
> To prevent squatters from stealing the libgit* crate names, I've
> published placeholder crates, which we can replace once we've fixed the
> build issues.

Thanks, that seems fine for now. I'll note that we're technically not required to even publish them on crates.io since Git repositories are supported, although of course crates.io would be convenient, and we can decide later on how to handle this most appropriately.

I think `cargo package` should do most (but not all) of the same checks, so we can use that as a testcase to see how things work and explore some options. We can even run it in CI if we like to avoid problems down the line.

-- 
brian m. carlson (they/them or he/him)
Toronto, Ontario, CA