<feed xmlns='http://www.w3.org/2005/Atom'>
<title>buildroot/package/cargo, branch 2018.02</title>
<subtitle>OpenPOWER buildroot sources</subtitle>
<id>https://git.raptorcs.com/git/buildroot/atom?h=2018.02</id>
<link rel='self' href='https://git.raptorcs.com/git/buildroot/atom?h=2018.02'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/'/>
<updated>2018-02-13T22:09:47+00:00</updated>
<entry>
<title>rustc: use RUSTC_{HOST,TARGET}_NAME</title>
<updated>2018-02-13T22:09:47+00:00</updated>
<author>
<name>Eric Le Bihan</name>
<email>eric.le.bihan.dev@free.fr</email>
</author>
<published>2018-02-13T07:21:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=f69c5192679de30e8af99885c6cd487e12ff0a25'/>
<id>urn:sha1:f69c5192679de30e8af99885c6cd487e12ff0a25</id>
<content type='text'>
utils/check-package complains as follows:

  package/rustc/rustc.mk:10: possible typo: RUST_TARGET_NAME -&gt; *RUSTC*
  package/rustc/rustc.mk:18: possible typo: RUST_HOST_NAME -&gt; *RUSTC*

As RUST_{HOST,TARGET}_NAME are related to the Rust compiler, it
sounds sensible to rename them to RUSTC_{HOST,TARGET}_NAME.

So update all rust related packages to use the new variables.

Signed-off-by: Eric Le Bihan &lt;eric.le.bihan.dev@free.fr&gt;
Signed-off-by: Thomas Petazzoni &lt;thomas.petazzoni@bootlin.com&gt;
</content>
</entry>
<entry>
<title>cargo: new package</title>
<updated>2018-02-05T13:57:48+00:00</updated>
<author>
<name>Eric Le Bihan</name>
<email>eric.le.bihan.dev@free.fr</email>
</author>
<published>2018-02-04T18:07:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/buildroot/commit/?id=990a7d14cfcd4773c0826f12770afa3a2b7f4275'/>
<id>urn:sha1:990a7d14cfcd4773c0826f12770afa3a2b7f4275</id>
<content type='text'>
This new package provides Cargo, the Rust official package manager.
Cargo is written in Rust and uses Cargo as its build system. It also
depends on other Rust packages.

Normally, a previously installed version of Cargo would be used to:

 1. Fetch the dependencies.
 2. Build the new version of Cargo, using the available Rust compiler.

But the fetching step prevents offline builds. So instead two features
of Cargo are leveraged: vendoring [1] and local registry.

First, a tarball of the build dependencies generated using `cargo
vendor` is fetched along with Cargo source code.

Then, the build process is as follows:

 1. The tarball of the build dependencies is uncompressed in a local
    registry.
 2. A snapshot of Cargo, provided by cargo-bin, builds the final
    version of Cargo.
 3. A configuration file telling Cargo how to cross-compile programs for
    the target is generated and installed.

Currently, only the host variant is provided.

[1] https://github.com/alexcrichton/cargo-vendor

[Peter: use src.fedoraproject.org, fix comment]
Signed-off-by: Eric Le Bihan &lt;eric.le.bihan.dev@free.fr&gt;
Signed-off-by: Peter Korsgaard &lt;peter@korsgaard.com&gt;
</content>
</entry>
</feed>
