When using the "assets" option, the path is relative to the workspace, as expected.
But when the cargo-deb is ran with the option --manifest-path, paths specified in assets are relative to where the cargo-deb command is running instead of the workspace directory as --manifest-path of cargo build is doing.
Hi,
When using the "assets" option, the path is relative to the workspace, as expected.
But when the cargo-deb is ran with the option --manifest-path, paths specified in assets are relative to where the cargo-deb command is running instead of the workspace directory as --manifest-path of cargo build is doing.