mirror of
https://github.com/zhigang1992/linux-configs.git
synced 2026-06-14 01:35:44 +08:00
da6b7ab712
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>
pacman
Table of Contents
- Overview
- Module Description - What the module does and why it is useful
- Setup - The basics of getting started with pacman
- Usage - Configuration options and additional functionality
- Reference - An under-the-hood peek at what the module is doing and how
- Limitations - OS compatibility, etc.
- Development - Guide for contributing to the module
Overview
Puppet module to configure and control PacMan package manager for ArchLinux. This module will ensure that the appropriate .conf file is installed.
Module Description
If applicable, this section should have a brief description of the technology the module integrates with and what that integration enables. This section should answer the questions: "What does this module do?" and "Why would I use it?"
If your module has a range of functionality (installation, configuration, management, etc.) this is the time to mention it.
Setup
What pacman affects
- Affects
/etc/pacman.confand controls thepacmanpackage. - Only works for ArchLinux.
Beginning with pacman
Usage
Currently:
class { 'pacman' :
iLoveCandy => true, # Optional
}
Reference
[*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.
Limitations
Pacman only functions on ArchLinux or ArchLinux derivatives.
Development
Pull requests are welcome.