This is Gentoo's testing wiki. It is a non-operational environment and its textual content is outdated.
Please visit our production wiki at https://wiki.gentoo.org
Project:Rust
| Gentoo Rust Project | |
|---|---|
| Description | The Gentoo Rust Project maintains the Rust toolchain and its related packages. |
| Project email | rust@gentoo.org |
| Lead(s) | none No lead election date set |
| Member(s) |
|
| Subproject(s) (and inherited member(s)) |
(none) |
| Parent Project | Gentoo |
| Project listing | |
The goal of this project is to provide proper packaging of Rust and Cargo for use within the Gentoo ecosystem. The project also maintains an eclass called cargo which can be utilized https://github.com/cardoe/cargo-ebuild to generate ebuilds for Cargo based projects to be built by a Gentoo package manager.
Bumping Rust and Cargo
Network-less builds
It is important to ensure that users of network-less builds or network sandboxing are able to build Rust and Cargo so you should test your ebuilds with the following:
/etc/portage/make.confAdding network-sandbox to FEATURES in PortageFEATURES="network-sandbox"
Ensure the binary is up to date
When bumping dev-lang/rust please ensure that dev-lang/rust-bin is kept at the same release. This avoids issues with people mixing versions that Portage can't reason around (note: add the bug #).
Cargo based projects
This includes Cargo itself (and soon Rust itself). You should always use https://github.com/cardoe/cargo-ebuild to gather the proper dependencies that need to appear in your ebuild. More than likely this utility will generate a proper ebuild for you. If the package in question contains a Cargo.lock file you MUST not change the dependencies that cargo ebuild generates because you will break offline installs.