Private crates that are added via path are not recognized as private

[fgo-ableton]

Describe the bug
Running cargo deny in a crate that pulls in other unlicensed crates from a path errors, even though the pulled in dependencies are marked as not published.

To Reproduce
Steps to reproduce the behavior:

1. Set deny.toml to ignore unlicensed private crates:

[licenses]
private = { ignore = true }

2. Import a different crate via path in Cargo.toml

[dependencies]
other_crate = { path = "/path/to/other/crate" }

3. Mark other crate as not published in its Cargo.toml

[package]
name = "other_crate"
...
publish = false

4. Running cargo deny check from parent crate returns an error even though it shouldn't
   error: other_crate 1.2.3 (path+file:///path/to/other/crate) is unlicensed

[djc]

FWIW, I'm also running into this. At work, I'm doing an experiment where I switch our Cargo workspace into two workspaces with a few shared crates outside the workspace. Those crates are used as path dependencies directly.

[leofidus]

For reference, we work around the imperfect ignore-private behavior by setting the license in each crate's Cargo.toml to license = "LicenseRef-OURCOMPANYNAME-Proprietary" and then adding that to the allowed licenses.

[Jake-Shadle]

Oops, I think that might be why I never noticed this since our main repo does this, I will take a look at this sometime this week.

[djc]

@Jake-Shadle thanks for fixing! Are you planning on pushing out a release soon?

[Jake-Shadle]

Yes, I'm just going to fix a few more bugs first.