snap: Ensure cargo-web doesn't erroneously adopt our workspace. #667

Merged
RAOF merged 1 commit from fix-snapcraft-build into master 2019-09-18 14:24:16 +00:00
RAOF commented 2019-09-18 12:57:17 +00:00 (Migrated from github.com)

Because snapcraft pulls the source into a subdirectory of Plume's source, and
Cargo will implicitly and recursively search parent directories for a [Workspace],
Cargo believes that cargo-web should be in Plume's workspace.

However, Cargo then errors out because Plume's [Workspace] stanza (entirely correctly)
doens't mention cargo-web.

Adding an empty [Workspace] stanza to cargo-web's Cargo.toml disables Cargo's implicit
search for a workspace to adopt, and avoids this problem.

Because snapcraft pulls the source into a subdirectory of Plume's source, and Cargo will implicitly and recursively search parent directories for a [Workspace], Cargo believes that cargo-web should be in Plume's workspace. However, Cargo then errors out because Plume's [Workspace] stanza (entirely correctly) doens't mention cargo-web. Adding an empty [Workspace] stanza to cargo-web's Cargo.toml disables Cargo's implicit search for a workspace to adopt, and avoids this problem.
trinity-1686a approved these changes 2019-09-18 13:32:49 +00:00
trinity-1686a left a comment
Owner

👍
(ci error is about uploading to plume-ci for live testing, not required here)

👍 (ci error is about uploading to plume-ci for live testing, not required here)
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Plume/Plume#667
No description provided.