If I have a repository that contains multiple crates - let’s say A and B, where A has a dependency on B - is it possible to publish A without also requiring B to be published? In particular, the A -> B dependency is specified using local path traversal:
[dependencies.B] path = "libs/B"
If the answer is yes, then how so? If the answer is no, then are there best practices for how to separate out logic that belongs in a separate crate, but that you don’t want published? Is there no other option than to use sub-modules inside the published crate?