Make cargo-build cargo workspace aware about cargo-bundle

[andrewdavidmackenzie]

Looking for spec details:
https://doc.rust-lang.org/cargo/reference/manifest.html#the-workspace-section

Determining if part of workspace, and which:

"The package.workspace manifest key (described above) is used in member crates to
point at a workspace's root crate. If this key is omitted then it is inferred to
be the first crate whose manifest contains [workspace] upwards in the filesystem."

         The Cargo.toml (found walking up the FS) could now have a workspace.exclude entry
         for this crate, meaning that this crate does not below to a workspace.

"Note that members of the workspaces listed explicitly will also have their path
dependencies included in the workspace"

QUESTION: If no workspace root directory is specified by the package.workspace key
do we just look in the parent directory for a Cargo.toml defining a workspace we belong
to, or do we have to walk up the file system until "/" to see if we can find a
Cargo.toml?

[mdsteele]

If I'm understanding cargo's behavior correctly, I think we have to walk all the way up the file system.

[andrewdavidmackenzie]

Yes, it looks like it. Looks like there can be empty directories between current directory and the workspace's root folder....so you need to walk all the way up until you find a Cargo.toml, then you can stop even if it doesn't declare a workspace.

[andrewdavidmackenzie]

See #47

[andrewdavidmackenzie]

@mdsteele any comments on the PR?
Prospects of merging (a cleaned up) version of it?

[andrewdavidmackenzie]

We can close this issue now, no?

A release with support for workspaces would be great now, and then I'd work on the original need to bundle resources from libs....

[mdsteele]

Thanks, I just published v0.3.0 with the latest changes.