diff options
author | intrigeri <intrigeri@boum.org> | 2010-12-15 09:47:57 +0100 |
---|---|---|
committer | intrigeri <intrigeri@boum.org> | 2010-12-15 09:47:57 +0100 |
commit | af8ecf1e9f6745a2c2d8c09b0f1e1d7c572981b9 (patch) | |
tree | 22b48aa33ff5386e7f31c4f3dec7101ea9b6e41b /README | |
parent | 4979889584b2b150e43f9930f5eccbf6cf5245fa (diff) |
Repair Exec['update_apt'] to run apt-get update when needed.
Move this Exec to a dedicated class that is not included by default i.e. we
default not to "apt-get update" on every Puppet run.
We now make use of this class in the apt::upgrade_package define to make sure
APT indexes are up-to-date before attempting package upgrades.
One may now use the following to ensure current packages are installed by
Package resources:
include apt::update
Package { require => Exec[apt_updated] }
Diffstat (limited to 'README')
-rw-r--r-- | README | 19 |
1 files changed, 10 insertions, 9 deletions
@@ -337,15 +337,16 @@ Use this resource to depend on or add to a completed apt configuration Exec[apt_updated] ----------------- -After this point, current packages can be installed via apt. It is usually used -like this: +After this point the APT indexes are up-to-date. -Package { require => Exec[apt_updated] } +This resource is usually used like this to ensure current packages are +installed by Package resources: -TODO -==== + include apt::update + Package { require => Exec[apt_updated] } -Sometimes -- especially when initially starting management or deploying new -packages -- a immediate update is really needed to be able to install the right -packages without errors. Thus a method should be devised to be able to specify -with high fidelity when a update should be run and when it is not needed. +Please note that the apt::upgrade_package define automatically uses +this resource so you don't have to manage this yourself if you need to +make sure APT indexes are up-to-date before a package upgrade is +attempted, but don't want "apt-get update" to happen on every Puppet +run. |