Open PetoMPP opened 5 months ago
The main reason for this is so that paths are relative to the crate root and shouldn't exit the crate boundary. That makes it easier when packaging/publishing crates even though relative paths are still allowed iirc.
While this may be an annoying limitation for crates in workspaces, those crates are still independent.
I am using the cargo-apk crate in a
workspace
enabled project and I had problems withassets
folder not being a subdirectory ofmanifest.parent
, so I implemented a small feature allowing for canonical paths with a fallback to previous handling.