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

Sammanfogat

RAOF merged 1 commit from fix-snapcraft-build into master

2019-09-18 14:24:16 +00:00

RAOF kommenterad

2019-09-18 12:57:17 +00:00

(Migrerad från github.com)

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 godkände dessa ändringar 2019-09-18 13:32:49 +00:00

trinity-1686a lämnade en kommentar

Ägare

👍
(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)

Logga in för att delta i denna konversation.

Inga granskare

Ingen milstolpe

Inget projekt

Inga tilldelade

2 Deltagare

Notiser

Förfallodatum

Förfallodatumet är ogiltigt eller utanför gränserna. Använd formatet "åååå-mm-dd".

Inget förfallodatum satt.

Beroenden

No dependencies set.

Reference: Plume/Plume#667

No description provided.

Rader
Kolumner