The title seems obvious. I've been developing a tool that I intended to publish as a single crate at crates.io. Internally, the repository had a few crates and I had assumed this is just an implementation detail, and that I would still be able to deploy it as a single crate, where the internal dependencies are bundled.

When I had trouble packaging the thing, I asked someone on discord and they explained to me (thanks!) that actually I needed to merge my crates into one ๐Ÿ’€

I wish I knew this earlier, now I think that adding cargo package to Ci in early stages of development really is a good idea.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] 5 points 3 days ago

If the crate were split, it might be for a good reason! You can upload split crates to crates.io. futures does that for exemple.

If in doubt, remember the Unix philosophy: do 1 thing, but do it well!

  • source