Matthew D. Steele

Looks like `cargo` sets [several](http://doc.crates.io/environment-variables.html) environment variables when executing commands (including `cargo run`) that wouldn't normally be present when running the binary directly. So the library could check e.g. `std::env::var_os("CARGO").is_some()`...

I'm not aware of any work being done on this. If you'd like to try to implement it, pull-requests would be welcome.

Sounds like a great idea to me!

Windows support in cargo-bundle is only half-implemented and doesn't work yet. It is waiting for a contributor who knows more about MSI packaging than I do and who has a...

Yes, that would be a welcome contribution! It would be great to have support for this. (It's nice to not need to install additional tools to be able to use...

This isn't currently possible, no. It's not immediately clear to me how it would work -- if this were a feature of cargo-bundle, how would non-cargo-bundled binaries depending on that...

I looked into this a little more, and it might be doable: - It looks like `Cargo.toml` has an [`include` field](https://doc.rust-lang.org/cargo/reference/manifest.html#the-exclude-and-include-fields-optional) that allows crates to include extra files as part...

I think each remote resource entry will probably need multiple attributes: URL, file checksum, repo tag/commit, etc. So each of these entries will need to be a toml table, not...

Being able to set a custom rpath is also important when bundling a binary as a Mac OS X app with embedded frameworks -- in this case, you need to...

Sure, if you can get it working and write some tests for it, a PR would be very welcome!