Closed naokiri closed 1 year ago
I've changed symlinks behavior in v1.41.0-beta.1. Please test it.
I believe 02ee084aa6d5b23cfac51eea253db10745b7c57f might have broken symlink assets in a different way.
In Config::resolve_assets
, glob::glob
is always used to resolve asset source paths, even for non-glob patterns.
Unfortunately glob::glob
also always tries to follow symlinks and has no option to disable that (see rust-lang/glob#63).
So if you try to package a dangling symlink (in the source tree that is), you will get an AssetFileNotFound
error.
Should I submit a PR to just skip globbing if preserve_symlinks
is enabled and the source is a symlink?
As a library developer, I want to build an lib*-dev.deb package.
Steps to reproduce
cargo deb
Expected
symbolic link is included in the deb package
Actual
Is there any workaround to make symlinks in deb package?