docs: fix misleading example of setting an env variable for a single command #3680
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- What I did
Fix a misleading example of setting an environment variable for a single command.
- How I did it
The
DEBIAN_FRONTEND
environment variable is used to control the interface by which debconf questions are presented to the user (seeman 7 debconf
). InDEBIAN_FRONTEND=noninteractive apt-get update && apt-get install -y
, theDEBIAN_FRONTEND
environment variable is only set for theapt-get update
command which does not ask debconf questions, and will not affect theapt-get install
command where these questions are actually asked. It should be the other way around.- How to verify it
The way environment variables work for single commands can be tested thus:
(In the last example, I'm running the commands in a subshell to avoid affecting the environment of my current shell.)
- Description for the changelog
Fix misleading example of setting an environment variable for a single command
- A picture of a cute animal (not mandatory but encouraged)