Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'Rust' |
Full page title (page_prefixedtitle) | 'Project:Rust' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=Rust Project
|Description=The Rust Project maintains the Rust toolchain and its related packages.
|Email=rust@gentoo.org
|IRC=#gentoo-rust
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|Members={{Project Member
|Developer=User:Cardoe
|IsLead=No
}}{{Project Member
|Developer=User:WilliamH
|IsLead=No
}}{{Project Member
|Developer=User:DJC
|IsLead=No
}}{{Project Member
|Developer=User:Cynede
|IsLead=No
}}{{Project Member
|Developer=User:Chutzpah
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|IsLead=No
}}
}}
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:
{{FileBox|filename=[[:/etc/portage/make.conf]]|title=Adding network-sandbox to FEATURES in Portage|lang=bash|1=
FEATURES="network-sandbox"
}}
=== Ensure the binary is up to date ===
When bumping {{Package|dev-lang/rust}} please ensure that {{Package|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.' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=Rust Project
|Description=The Rust Project maintains the Rust toolchain and its related packages.
|Email=rust@gentoo.org
|IRC=#gentoo-rust
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|Members={{Project Member
|Developer=User:Cardoe
|IsLead=No
}}{{Project Member
|Developer=User:WilliamH
|IsLead=No
}}{{Project Member
|Developer=User:DJC
|IsLead=No
}}{{Project Member
|Developer=User:Cynede
|IsLead=No
}}{{Project Member
|Developer=User:Chutzpah
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|IsLead=No
}}
{{Project Member
|Developer=User:Kentnl
|IsLead=No
}}
}}
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:
{{FileBox|filename=[[:/etc/portage/make.conf]]|title=Adding network-sandbox to FEATURES in Portage|lang=bash|1=
FEATURES="network-sandbox"
}}
=== Ensure the binary is up to date ===
When bumping {{Package|dev-lang/rust}} please ensure that {{Package|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.' |
Wiki