aboutsummaryrefslogtreecommitdiff
path: root/manifests/preferences_snippet.pp
AgeCommit message (Collapse)Author
2013-02-16Don't check for a package priority to be set when removing an APT ↵intrigeri
preferences snippet. The problem I'm facing is that the sanity checks prevent one from using a simple: apt::preferences_snippet { "bla": ensure => absent } So, first set a default value for the `priority' parameter, so that it's not required anymore. Second, add a sanity check to error out when priority is not set, to get the safe old behaviour. Then, wrap all sanity checks about arguments within a "if $ensure == 'present'" block.
2013-01-02Apply code style corrections from puppet-lintGabriel Filion
Signed-off-by: Gabriel Filion <lelutin@gmail.com> + more linting by intrigeri. Conflicts: manifests/apticron.pp manifests/cron/dist_upgrade.pp manifests/cron/download.pp manifests/dist_upgrade/initiator.pp manifests/init.pp manifests/listchanges.pp manifests/preferences.pp manifests/preseeded_package.pp manifests/proxy_client.pp manifests/unattended_upgrades.pp manifests/update.pp
2012-09-20Make apt::preferences_snippet place files in /etc/apt/preferences.dGabriel Filion
Since Debian Squeeze, apt supports a .d directory for preferences (pinning). Simplify management by just placing files inside this .d directory. This removes the need for concat and concat::fragment resources, so removes the dependency on the concat module. It also removes the need for a moduledir that was needed for the concat module magic, so we also get rid of the dependency on the common module. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2012-06-18Make apt::preferences_snippet support Puppet < 2.7 again, when the 'package' ↵intrigeri
parameter is not set. Details: https://labs.riseup.net/code/issues/3467 https://labs.riseup.net/code/issues/3468
2012-06-08Allow passing arbitrary Pin value to apt::preferences_snippet.intrigeri
Closes: Redmine#3467.
2012-06-08Support multiple APT preferences snippets for the same package name pattern.intrigeri
This is implemented by adding a "package" parameter to apt::preferences_snippet, so that define names can be kept unique while the package names are not necessarily. Closes: Redmine#3468.
2012-04-11use the correct namemh
2012-04-11migrate concatenated_file to the concat modulemh
2010-12-07format standardizationMicah Anderson
2010-10-28put the file at the right place & fix typosmh
2010-10-25Fix apt::preferences::absentGabriel Filion
Currently, setting the $custom_preferences variable to false fails because of the /etc/apt/preferences concatenated_file being re-defined. Fix this by setting dependencies on the resource only when we expect to create the /etc/apt/preferences file. Also, since there is no "ensure" parameter to concatenated_file, use a simple file resource to ensure that it is removed. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2010-10-25refactor: simplify and remove inline contentGabriel Filion
Simplifications: make apt_conf_snippet repeat less code, make code that generates sources.list more concise. Remove all inline content in favor of templates and static files. The ability to include sources for static files was needed for the main 'preferences' file, so it was added to the preferences_snippet define. Signed-off-by: Gabriel Filion <lelutin@gmail.com>
2010-10-17empty line between snippetsmh
2010-10-17fix classnamemh
2010-10-17fix modules directory stuffmh
2010-10-17improve prefrences snippetmh
2010-10-17introduce preferences snippetmh
Now, we have the possibility to externally add snippes, so that we can preferences for packages that are for example only in backports or unstable.