15 ms·
Android CLI can write a tool that wraps android-cli and automatically passes the flag based on an env variable. How would Google have enough data about a brand
by gowld 6mo ago
Android CLI can write a tool that wraps android-cli and automatically passes the flag based on an env variable.
How would Google have enough data about a brand new product without collecting that data?
- tredre3 6mo ago> How would Google have enough data about a brand new product without collecting that data? They wouldn't. But on the other hand, they probably have a large amount of in-house Android app developers on whom they can conduct such metrics collection. I wouldn't expect outsiders to have vastly different workflows, because when you get out of the happy path with Android all you get is pain.
- Onavo 6mo agoOutsiders probably do have vastly different workflows. Google internally love to stick Bazel on everything and that's quite different (and overly complicated) compared to the usual Gradle route.
- panzi 6mo ago`alias android-cli='android-cli --no-metrics'`
- SJMG 6mo agoUh do aliases load in non-interactive shells?
- EdwardDiego 6mo agoYou could export BASH_ENV to have Bash processes source a given file at startup. Zsh has .zshenv, and Fish just has config.fish for everything with the ability to guard certain things within it to login only or non-interactive only.
- figmert 6mo agoCreate a wrapping binary instead mkdir -p ~/.local/bin printf '#!/usr/bin/env sh\nexec android-cli --no-metrics "$@"' > ~/.local/bin/android-cli echo 'PATH="$HOME/.local/bin:$PATH"' >> ~/.zshenv
- yorwba 6mo agoI'm pretty sure this will just call itself in a loop. You need to use the absolute path to the wrapped binary to distinguish it from the wrapper.