This distinction is described in that same link. Workspaces exist mainly to settle other concerns, such as having a single source of compiled dependencies with a shared dependency lock. If so, then why should I bother with workspace at all? The current behavior could be linked with packaging being primarily part of publishing, so this could probably be improved. For packaging, it is a limitation at the time of writing. One can still publish crates in a workspace, so long as this is done in the right order. Or, using cargo-workspaces: cargo workspaces publish Whenever you have a project with many crates in a single workspace and wish to publish them on crates.io, you would start with the crate without dependencies and work your way up to the other crates. Creating tarballs also happens to have the same constraints at the moment, so it is not possible if they are not meant to be published. Typo on the torstol seed, reduced from 6 to 55 xD Good changes overall. For publishing this is relatively obvious, since consumers also need to be able to fetch and build transitive dependencies. 14 torstol seeds from wintertodt with 133 crates to go, some of which are 10k+. Packaging and publishing crates requires all dependencies of said crate to also be available in a registry. Required by package `foo_1 v0.1.0 (E:\Works\Experimentals\rust-workspace\target\package\foo_1-0.1.0)` Verifying foo_1 v0.1.0 (E:\Works\Experimentals\rust-workspace\foo_1) Packaging foo_1 v0.1.0 (E:\Works\Experimentals\rust-workspace\foo_1) Warning: manifest has no description, license, license-file, documentation, homepage or repository. It can't found the foo_2 package.įoo_2 = Įrror message: PS E:\Works\Experimentals\rust-workspace> cargo package -workspace Is this an intended behavior? if so, then why should I bother with workspace at all ? Which is pretty weird, since I specifically add a local path on the dependencies. Dog bed, cat bed, indoor dog house, dog kennel, dog crate, dog furniture. Modern dog and cat house with acrylic door and fabric roof PetSo. It makes it easier to check that things in libs/ don ’ t use things from crates/. It probably makes sense to extract all such crates into a separate top-level folder, libs/. If you do want to publish a subset of crates with proper semver API, be very deliberate about them. Made of solid pine wood, cotton canvas and polyester fabrics. Use version '0.0.0' for internal crates you don ’ t intend to publish. It displays: no matching package named "foo_2" found. Contemporary pet tent/house with soft cushion/bed. But as soon as one package depends on the other the cargo package will fail. If all of the package were independent from each other, cargo package would run successfully. It runs successfully with cargo run or cargo build I create a "workspace" with several folder within it following the tutorial I read here ConfectioneryHealthy SnackingNovelty Confectioner圜hocolatePetsPets Best SellersDogDog Crates, Playpens & KennelsDog BedsDog Bowls & FeedingDog ToysDog.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |