Skip to content

Thomashighbaugh/dotfiles

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

README: Dotfiles

Never Mind the Bullocks, Here's the Dotfiles!

There's unlimited supply
And there is no reason why

...
And you thought that we were faking
That we were all just money making
You do not believe we're for real

Or you would lose your cheap appeal?

Don't judge a book just by the cover
Unless you cover just another
And blind acceptance is a sign
Of stupid fools who stand in line
- The Sex Pistols "EMI" from the album Nevermind the Bullocks, Here's the Sex Pistols

pictoral representation of the state of the repository at any given moment depicting palm trees engulfed in flames due to nearby nuclear testing

Introduction

The files in this repository are my configurations powering my archlinux setup and the installation scripts that place them into the directories the system reads them from, after first installing the software that is.

This means that you are feasting your eyes upon a bare git repository featuring a home-rolled installation and configuration management system written by yours truly that has been derived from the organic process of reinstallations and daily management of these files and my system over all.

Installation Scripts

At this point, the history of this repo reflects my use of a litany of tools to arrive a useful configuration following the need to install or reinstall, from ansible to Makefiles. I have settled, for now, on using the much more precise but fickle set of BASH scripts found in the `install` subdirectory.

My goals for the installation process include:

  • symlinking files within this repository to various locations in home so they are editable without needing to fuss with copying them over to the intended location again
  • copying over set-and-forget configurations I like having system wide and do not edit, thus need not symlink
  • adding in the extra package repositories I use to save me compule time
  • cloning the other configurations I back up to git, in the locations they are expected by the system to be in, but are too big and unruly to contain within this repository. Like my awesomewm configuration
  • Menu driven process breaking up installation into several portions that are idempotent (can run them multiple times over and over without changing the result, important for debugging Tom style)
  • Output to a log file to ease debugging when things go wrong, as they so often do