Skip to content
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

Jump to bottom

RFC: Add option to mark a crate "private" so it's not publishable to crates.io #2202

Closed
erickt opened this issue Dec 8, 2015 · 2 comments · Fixed by #2321
Closed

RFC: Add option to mark a crate "private" so it's not publishable to crates.io #2202

erickt opened this issue Dec 8, 2015 · 2 comments · Fixed by #2321
Labels
E-easy Experience: Easy

Comments

@erickt
Copy link
Contributor

erickt commented Dec 8, 2015

npm has a helpful "private" option that prevents an internal package from being published. This would be really useful as people develop internal applications, or a project like Servo where only some crates can be safely published.
@alexcrichton alexcrichton added the E-easy Experience: Easy label Dec 8, 2015
@JanLikar
Copy link
Contributor

Like this?

[package]
name = "foo"
private = true

@alexcrichton
Copy link
Member

@JanLikar yeah that's what I was thinking

@JanLikar JanLikar mentioned this issue Dec 16, 2015
Closed
@felixc felixc mentioned this issue Jan 10, 2016
Closed
@JanLikar JanLikar mentioned this issue Jan 26, 2016
Merged
bors added a commit that referenced this issue Jan 26, 2016
@bors
Auto merge of #2321 - JanLikar:private-crate, r=alexcrichton
6ffd134 
I Accidentally closed #2218, this is the new PR.

[Fix #2202]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
E-easy Experience: Easy
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add field private to Cargo.toml JanLikar/cargo
3 participants
@alexcrichton @erickt @JanLikar