Skip to content

Update contribution guidelines to use --index #1086

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 28, 2017
Merged

Update contribution guidelines to use --index #1086

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
75dbb19
Update contribution guidelines to use --index
Deedasmi Sep 26, 2017
03a95c5
Add note for older cargo versions
Deedasmi Sep 26, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -428,13 +428,14 @@ live crates.io, you won't be able to publish that crate locally.
In your crate directory, run:

```
cargo publish --host file:///path/to/your/crates.io/checkout/tmp/index-co
cargo publish --index file:///path/to/your/crates.io/checkout/tmp/index-co
```

> If you're using an older version of cargo you should use `--host` instead of `--index`.

where `file:///path/to/your/crates.io/checkout` is the directory that you have
crates.io's code in, and `tmp/index-co` is the directory with the git index
that `./script/init-local-index.sh` set up. [Yes, `host` dosen't really make
sense as a name for this flag](https://github.com/rust-lang/cargo/issues/3797).
that `./script/init-local-index.sh` set up.

Note that when you're running crates.io in development mode without the S3
variables set (which is what we've done in these setup steps), the crate files
Expand Down