cargo-ebuild VS cargo-release

In Gentoo, Rust crates are just normal files to be downloaded in order to build a given package. The package pins (and checks the hashes of) the crate deps, and builds using cargo --offline. There is no serde/clap/etc packages, just ripgrep/librsvg/etc packages. There is no need to patch all packages to use the same serde crate version. Packaging a Rust program in gentoo is pretty much automatic.

Then, I went through like 3 different pages on gentoo and learned how to make my own rebuild using this... But after setting up my custom repo and making sure it had the right permissions, manifest, etc. the ebuild failed on account of not being able to find the Config.yoml file it needed, which exists in the directory I built the ebuild from. I think I am just SOL on this, and will have to probably find a different approach

FWIW it's worth for portage (Gentoo) there is g-sorcery[0], which can create ebuilds for Emacs (m/elpa) and python packages automatically. Similarly there is also cargo-ebuild[1] which can create ebuilds for rust programs/libraries, including a list of all dependencies with hashes.

I've successfully used cargo-ebuild in the past to create ebuilds automatically, it's a breeze. I'd be surprised if similar tools didn't exist for deb/rpm based distros.

[0]:https://github.com/jauhien/g-sorcery

[1]: https://github.com/cardoe/cargo-ebuild

I'm working on a custom repository where I intend to write ebuild files for packages that's not supported by Gentoo's repository. Right now, I'm trying to write an ebuild file for xplr, which is a Rust project that uses the Cargo build system. Initially, I used the cargo-ebuild tool, which generated the file xplr-0.14.3.ebuild.

Maybe you already know, but specifically for making Rust ebuilds and filling the CRATES variable there's a tool cargo-ebuild to automatically extract that from Cargo.toml.

I have zero issues with Gentoo's Rust and Rust-using packages. I use rustup's Rust and cargo install for development, and maintain a gentoo package using cargo ebuild.

My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.

I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including

- You can't as easily introspect the process

- You can't as easily recover from failure

- Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult

- When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version

I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23

[0]: https://github.com/crate-ci/cargo-release

[1]: https://github.com/MarcoIeni/release-plz/discussions/1019

You should combine step 1 and 2 with CI. Just tag a version in your git, push to remote and have CI auto build a release for you.

Use github actions or other setup for other backends.

Or go nuts with cargo-release.

https://github.com/crate-ci/cargo-release

https://github.com/cargo-bins/release-pr

tools like cargo-release

Just to check, are you aware of cargo-edit's cargo-set-version or cargo-release?

I released my first crate that provides a derive macro to easily obtain a name of a current variant in an enum as a string. I did it mostly to learn about procedural macros and the process of releasing a crate. I then found out there is strum which does this and much more. Nonetheless, I learned a lot and I found couple of nice tools like ```cargo-release and git-cliff.

I'll note there is an issue in the cargo-release repo where this kind of workflow is wanted. https://github.com/crate-ci/cargo-release/issues/119

cargo-release is on about the same level of features used

cargo-release automates the release process for your crate. For example, with clap, all I do is add entries to the CHANGELOG and run cargo release patch and cargo-release takes care of updating files, publishing to crates.io, tagging, and pushing.

Yes, developers from all three tools were sharing ideas with each other recently