upvote

points

by sunaookami10 hours ago |
comments
upvoteby gowld9 hours 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?

reply
upvoteby panzi6 hours ago|
parent|
next
[-]
`alias android-cli='android-cli --no-metrics'`
reply
upvoteby SJMG4 hours ago|
parent|
[-]
Uh do aliases load in non-interactive shells?
reply
upvoteby figmert2 hours ago|
parent|
next
[-]
Create 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
reply
upvoteby EdwardDiego2 hours ago|
parent|
prev|
[-]
You 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.

reply
upvoteby tredre37 hours ago|
parent|
prev|
[-]
> 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.

reply