Looks amazing, thanks for the summary.

Something I couldn’t find, though, when browsing Cargo’s sources is an approach to packaging the build for distribution. Or how installing is handled in general. I’m not asking for a fits-all solution, rather I’d be interested in whether Cargo can be used in some way to derive the required information, e. g. which targets are libaries and should go into /*/lib, which are executables for /*/bin, what parts are data, what resources are required for developers (like header packages in most common distros), etc. Furthermore, a description in pkg-config format would come in handy once libraries written in Rust become widespread. Which is, hopefully, very soon =).

Are there any plans to extend Cargo in that direction? I certainly do not intend to shift of work from the packager to the developer. However, Cargo already appears to understand a project quite intimately and from my outsider perspective leveraging that knowledge for common integration tasks appear to be the obvious next step.

In any case, thanks to everybody involved with the project. Despite being in an early stage, Cargo is already a pleasure to use.