Katharina Fey

Hey, thanks for this PR. Could you try rebasing your branch? I merged a bunch of PRs that have been open for way too long :see_no_evil: Once that's taken care...

I'm not sure it's possible to get the version of the compiler a Rust binary was built with after compilation. At most we could try to include that statically in...

ping @phansch did you ever finish the build script so we can steal it? :slightly_smiling_face:

Yay a :bike: :house: ! Renaming the setup macro is definitely a good idea, although I'm not sure I'm happy with any of the suggestions so far :wink: Repeating the...

:tada: So #48 is now on `master` and if you look at the PR #50 we might want to release this only under a `2.0.0` because it can have severe...

I just branched off fed6fda1a4827c00e9c43e580f2ea20ed9ee9b0b into it's own branch: `1.0.0-maintenance` which is where all bug fixes for the `1.0.0` compatible versions can be accumulated. This means that `master` is now...

I think what's absolutely vital for this crate is to not re-invent the wheel. We don't want to replace `configure`, at most I think what we should consider this crate...

@killercup When it comes to automatically generating debian packages (and there is already [cargo-deb](https://github.com/mmstick/cargo-deb) for that) I think it's even more important to generate **source** packages for distributions to include...

@Aaronepower Well, that's all well and good and yea maybe there are some things in the `cargo install` pipeline that aren't very nice right now. But to target that at...

@ayosec We don't have to support *all* package managers. Creating source `deb` files, source `rpm` files would be a great start. Yea sure, making `snap` and `flatpak` packages is also...