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

Publish lambda-http crate on crates.io? #67

Closed
adimarco opened this Issue Dec 31, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@adimarco
Copy link

adimarco commented Dec 31, 2018

The lambda-http crate doesn't seem to be published on crates.io, which means the only way to use it in a project is to reference this git repo directly in Cargo.toml, which is not exactly ideal.

i.e., I got it to build with

[dependencies.lambda_http]
git = "https://github.com/awslabs/aws-lambda-rust-runtime"

but it would be much nicer to specify it as a regular crates.io dependency.

Are there any plans to publish the lambda-http crate?

@davidbarsky

This comment has been minimized.

Copy link
Member

davidbarsky commented Jan 1, 2019

doesn't seem to be published on crates.io, which means the only way to use it in a project is to reference this git repo directly in Cargo.toml, which is not exactly ideal.

Agreed, yes. It's not ideal. We intend to publish soon, as it's still partially under development (see #64, hyperium/http#286). I think me and @sapessi should have a roadmap for the 0.2 release that you can track. We'll cover that during our standup tomorrow.

Until then, would a 0.0.1 release on crates.io be okay, or would you rather have a git dependency until a 0.1 release?

@adimarco

This comment has been minimized.

Copy link

adimarco commented Jan 1, 2019

I just wanted to make sure that publishing it wasn't something that got overlooked by accident. No rush if it's still under early, active development.

The git dependency is fine for now - I'm just tinkering. Thanks for the response.

@davidbarsky

This comment has been minimized.

Copy link
Member

davidbarsky commented Jan 3, 2019

Understood. I'll close this issue for now. Feel free to reopen or create another issue if you run into anything else.

@davidbarsky davidbarsky closed this Jan 3, 2019

@sapessi sapessi added this to the 0.2 milestone Jan 25, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment