Skip to content

Feature request: support for building unreleased crates #206

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.

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

Closed
pkgw opened this issue May 16, 2018 · 2 comments
Closed

Feature request: support for building unreleased crates #206

pkgw opened this issue May 16, 2018 · 2 comments

Comments

@pkgw
Copy link

pkgw commented May 16, 2018

Some crates with system dependencies are a bit tricky to get their docs building in the docs.rs system. In several cases, I've needed to publish a series of "new" releases to crates.io to trigger new docs.rs builds to try to fix various problems with my docs.rs builds. This isn't the end of the world, but it's not great to have to cut new releases just to iterate on these problems.

This is the case even if you spin up your own docs.rs Vagrant image, since the underlying command still will only fetch crates from crates.io.

It would be great if cratesfyi could pick up a subcommand that would attempt a build on a crate stored
locally. Something like

cargo run -- build local-crate /path/to/source

This would make it possible to iterate locally instead having to publish a new release for every attempted change.

@jyn514
Copy link
Member

jyn514 commented Dec 7, 2019

This was implemented in #460.

@jyn514 jyn514 closed this as completed Dec 7, 2019
@pkgw
Copy link
Author

pkgw commented Dec 9, 2019

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants