Files
Tom Swartz da6b7ab712 Refactor layout to allow Puppet to deploy files
Move files to a 'puppetized' layout.

Puppet will then look to manifests/default.pp to install selected
software packages.

This will allow for easier deployment of a new setup, and specific hosts
may receive only the modules that they need. (raspi only needs mutt,
tmux, and irssi, for example)

Tested-on: heimdall <04 Jun 2014>
2014-06-04 11:12:23 -04:00

56 lines
1.0 KiB
Puppet

# == Class: pacman
#
# Configures PacMan package manager for ArchLinux.
#
# === Variables
#
# Here you should define a list of variables that this module would require.
#
# [*iLoveCandy*]
# Inserts 'easter egg' configuration option into pacman.conf
# Changes the standard [###--] progress bar with [---C o o ]
# styled after the 1980's 'Pacman' game.
#
# === Examples
#
# class { pacman:
# iLoveCandy => true,
# }
#
# === Authors
#
# Tom Swartz <tom@tswartz.net>
#
# === Copyright
#
# Copyright 2014
#
class pacman (
$iLoveCandy = false,
){
case $::operatingsystem {
Archlinux : {
$supported = true
}
default : {
$supported = false
}
}
exec { 'pacman-update' :
command => '/usr/bin/pacman -Syy',
subscribe => File['pacman.conf'],
refreshonly => true,
}
if ($supported == true) {
file { 'pacman.conf' :
path => '/etc/pacman.conf',
content => template("${module_name}/pacman.conf.erb"),
notify => Exec['pacman-update'],
owner => '0',
group => '0',
}
}
}