Publish on crates.io? #2
Comments
|
Yes, this would be a very useful crate. @donbright would you like a PR with some docs to make it more suitable for crates.io and docs.rs? |
|
Hi! Been following this GitHub Issue since it was opened. I'm working on a project that utilizes this (wonderful) crate. @donbright is it okay if I publish this to crates.io on a fork? I'll of course still attribute you in the copyright, and happily give you ownership of the crates.io name if you decide you want it. Thanks so much for writing this! |
|
hehe thanks @frewsxcv .. i was thinking about doing the same thing! |
|
Forked and published: https://github.com/frewsxcv/earcutr https://crates.io/crates/earcutr |
|
yeah uhm go for it? sorry for delay ... long story . . . i couldnt really publish it on crates. another long story. fun fact - mapbox already ported their library to rust, which i did not know when i wrote this. mine is just "100% safe" rust thanks |
The [published crate](https://crates.io/crates/earcutr) corresponds to @frewsxcv's repo, which has incorporated some additional changes since forking from https://github.com/donbright/earcutr I think it'd be least confusing to point users to the repo corresponding to the published crate. See donbright/earcutr#2 (comment) /cc @frewsxcv, @donbright
Hi! We're using this package as part of our rust implementation of a new format for packing OSM data. Do you have any intention of publishing this on the crates.io website? Otherwise, it seems like I'll have to add your git repository as a submodule etc, which isn't ideal.
Thanks @donbright !
The text was updated successfully, but these errors were encountered: