error: environment variable `VAGGA_VERSION` not defined --> src/config/config.rs:56:26
vagga xxxfrom a foreign project it can't stole your ssh keys or similar. You can share configs either but putting them in git submodule (and updating manually), or you can
mount --binda subdirectory into several places. Or you can use external-volumes to overcome that limiation (although, it would require configuring them for every user).
mount --bindor just copy thing in ad hoc way.
Alternatively, you can also make a command which fetches mixin remotely before the first start.
ln -s ../include.yaml include.yaml?
I'd like something of "best practice" advice
I usually recommend as independent repos as possible, i.e. that you can
vagga run in any one. And use git submodules for thing that can't be fetched from package repos. The big advantage of submodules that you can always
mount --bind on top. Not sure it's anywhere in the docs.
#!/bin/bash sudo apt install musl-tools -y git clone https://github.com/tailhook/vagga cd vagga/ git checkout v0.8.1 rustup target add x86_64-unknown-linux-musl cargo build --target x86_64-unknown-linux-musl
$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster $ uname -a Linux lua 5.3.0-0.bpo.2-amd64 #1 SMP Debian 5.3.9-2~bpo10+1 (2019-11-13) x86_64 GNU/Linux
The documentation does not mention anything about VAGGA_VERSION, as far as I read. And I didn't read much... just jumped to Installation and followed instructions.
error: environment variable `VAGGA_VERSION` not defined --> src/config/config.rs:56:26 | 56 | .current_version(env!("VAGGA_VERSION").to_string())) | ^^^^^^^^^^^^^^^^^^^^^ error: environment variable `VAGGA_VERSION` not defined --> src/launcher/mod.rs:94:19 | 94 | Print(env!("VAGGA_VERSION").to_string()),
write-mode: transient-hard-link-copy. But it's generally not common case to test installation via vagga on every build.