Jens Reimann

True. Maybe have something like `--skip-download ` where `` is an enum of the tools we have. And `--skip-download` accepts a list of values. So one could do: ``` trunk...

Doesn't plain `env!` from Rust work for that?

This works during compile time: https://doc.rust-lang.org/std/macro.env.html So when you use: ```rust fn my_foo() -> String { env!("MY_FOO").into() } ``` And compile it with: ```bash env MY_FOO=bar cargo build ``` Then...

Hm. I am still not sure I understand what trunk should exactly do here? Re-reading the `.env` file during runtime?

Ok, just summing this up, the idea is to: * Have trunk export the env-vars (possibly filtered) into a JSON struct * Having that JSON struct assigned in the `index.html`...

Could you come up with a PR for this?

IIRC a lot of features internally are triggered by the "release" flag. I think we should move away from this and have individual settings. And having `--release` only change the...

I haven't used it in quite a while. So I am not sure I can help.

Haven't used it in a while, but IIRC it should work like this: https://github.com/ctron/rpm-builder/blob/3095c0ed0ef27c3baaa87f898f18c8ea8a7733ce/src/it/test10-defaultname/pom.xml#L58

The maven-rpm-plugin is something different. So you need to define it in the `pom.xml`, and it does support variable substitution. Should also work with env-vars.