I get workspace with 2 subprojets, but when running cargo aur, get Error: missing field package at line 1 column 1
Originally created by @Ludea on GitHub (Feb 6, 2023).
Original GitHub issue: https://github.com/fosskers/cargo-aur/issues/17
workspace seems to be not supported.
I get workspace with 2 subprojets, but when running `cargo aur`, get ` Error: missing field package at line 1 column 1`
doesn't work because binaries are into /workspaceroot/target/release/XXX and not /workspaceroot/workspacemember/target/release/XXX
@Ludea commented on GitHub (Feb 7, 2023):
doesn't work because binaries are into `/workspaceroot/target/release/XXX` and not `/workspaceroot/workspacemember/target/release/XXX`
@ozwaldorf commented on GitHub (Jun 15, 2023):
Related:
With a structure like so:
```
crate1/
- crate2/
- src/
- lib.rs
- Cargo.toml
- src/
- bin.rs
- lib.rs
- Cargo.toml
```
It fails when the root cargo toml uses workspace.package keys for anything in the package section, for example:
```
[package]
...
license.workspace = true
[workspace]
members = ["crate2"]
[workspace.package]
license = "MIT"
```
One possible workaround for the detection of target/ would be to symlink to target/ from <subcrate>/target/.
@fosskers commented on GitHub (Oct 2, 2023):
One possible workaround for the detection of `target/` would be to symlink to `target/` from `<subcrate>/target/`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Ludea on GitHub (Feb 6, 2023).
Original GitHub issue: https://github.com/fosskers/cargo-aur/issues/17
workspace seems to be not supported.
I get workspace with 2 subprojets, but when running
cargo aur, getError: missing field package at line 1 column 1@fosskers commented on GitHub (Feb 7, 2023):
Would it work if you ran
cargo aurwithin the subcrate?@Ludea commented on GitHub (Feb 7, 2023):
doesn't work because binaries are into
/workspaceroot/target/release/XXXand not/workspaceroot/workspacemember/target/release/XXX@ozwaldorf commented on GitHub (Jun 15, 2023):
Related:
With a structure like so:
It fails when the root cargo toml uses workspace.package keys for anything in the package section, for example:
@fosskers commented on GitHub (Jun 21, 2023):
Thanks for the extra info.
@fosskers commented on GitHub (Oct 2, 2023):
One possible workaround for the detection of
target/would be to symlink totarget/from<subcrate>/target/.support rust workspaceto [GH-ISSUE #17] support rust workspace