search

hotg-ai / rune

Rune provides containers to encapsulate and deploy edgeML pipelines and applications
Apache License 2.0
134 stars 15 forks source link

Unable to publish to crates.io due to naming conflict #222

Closed Michael-F-Bryan closed 3 years ago

Michael-F-Bryan commented 3 years ago

We can't publish the rune-XXX crates to crates.io because a Rune project already exists and it already has a bunch of rune-XXX crates.

I'm guessing the best solution would be to publish as hotg-rune-XXX, but for crates like hotg-rune-proc-block-macros the names are starting to get ridiculously long.

@akshr and @kthakore, can you think of a better solution?

This is blocking #210.

kthakore commented 3 years ago

Could we do a private crates? Is hmr-* taken?

Michael-F-Bryan commented 3 years ago

Could we do a private crates?

I don't think so. There's no such thing as a private crate on crates.io.. plus making it private probably doesn't line up with our open source plans, does it?

We could leave things as git dependencies, but that gives the feel of a project undergoing massive churn instead of something which has versioning guarantees.

Is hmr-* taken?

Nope, so we could always use hmr-rune-XXX as the prefix (e.g. hmr-rune-codegen or hmr-rune-cli). That said, Hammer is a different project to Rune, whereas hotg is the organisation behind Hammer and Rune.