From 25e2eaddc9d2261685811114efe3c9ae78dc259c Mon Sep 17 00:00:00 2001
From: Cody P Schafer <dev@codyps.com>
Date: Mon, 6 Jul 2015 15:03:49 -0400
Subject: [PATCH] readme update: rust is no longer breaking cargo every other
 release, and we've completed some of the TODO items

---
 README.md | 24 +++---------------------
 1 file changed, 3 insertions(+), 21 deletions(-)

diff --git a/README.md b/README.md
index a0b1e56..648cdbf 100644
--- a/README.md
+++ b/README.md
@@ -35,32 +35,14 @@ ecosystem get their act together, you'll need to supply patches to the
 misbehaving packages. See `recipies/cargo/cargo_*.bb` for an example of how to
 do this.
 
-## Cargo
-
-Cargo may not work with the latest rust.
-You can try either:
-
-  - use the system cargo:
-
-    CARGO_PROVIDED = "cargo-native"
-    ASSUME_PROVIDED += "${CARGO_PROVIDED}"
-
-  - or have cargo use a rust snapshot
-
-    PACKAGECONFIG_append_pn-cargo-native = " rust-snapshot"
-
-Note that using the rust-snapshot currently has issues with the targets
-provided by bitbake, for it to work we need to generate the same target.json
-that we do for the main compiler.
-
 ## TODO
 
- - Include downloaded stage0 snapshot in `SRC_URI`
  - -crosssdk and -buildsdk packages
  - -runtime? (install target libraries on target)
- - Add SRC_URI components so that cargo doesn't use the network
- - Convince cargo (via env vars or patching) not to use '$HOME/.cargo' for storing downloaded source code
  - Upstream local rustc patches for libdir and bindir support
+ - add bitbake fetch support for crates.io
+ - add required cargo package registry clones in SRC_URI to prevent the need
+   for network when building.
 
 ## Pitfalls