Make sure we configure the proxy before doing apt-get update. #41
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.
In the case your machine can't access the internet except through a proxy, you want it to be set before you do the apt-get update!
I used a
notify
dependency just in case you forgot to set the proxy in the first place (or mistyped it) and thus had the apt-get update failing. Without thenotify
, the apt-get update wouldn't get executed after you fix the proxy issue, as the sources.list and sources.list.d would have been set in the first (failing) run (I mean, unless you usealways_apt_update
, but that's another story).I didn't set a dependency on the python-software-properties package because:
apt::ppa
(see Move Package['python-software-properties'] to apt:ppa #40)Class['apt'] -> Package <| |>
which would then guarantee the apt-get update will be executed before you install any package