Kornel
Yeah, that's likely. The assets have been changed a few times.
How do you usually make the debug variant? * Which tools do you use to extract debug info to a separate file? * How is that structured in the debian...
Oh, that looks like a regression.
Ah yes, I completely forgot about symlinks. cargo-deb reads files and inserts the content in the archive. It should check whether the file is a symlink and insert it as...
@bcmyers Could you merge this and make a release?
If you set `RUST_LOG=debug`, you'll get (too much) info from Cargo. It looks like the problem is the `path`, which becomes invalid after cargo-outdated copies the project to a temporary...
It'd be ideal if Cargo exposed its dependency resolution algorithm as a library. Then even the "temp workspace" hack wouldn't be needed — cargo-outdated could read and evaluate data straight...
Performance is not my primary concern. The changes I'd like to make are: * support for color profiles. AFAIK currently resvg ignores them. * hardening against files that are too...
I've released cargo-deb 1.5.0 with our internal library functions exposed: https://docs.rs/cargo-deb/ Currently it's just exposing more or less what we call in our `main()`, so the API may be weird/too...
Similar problem with `#include `, which expands to compiler-specific builtins: > illegal undefined variable; check whether a real C compiler accepts this: __builtin_expect