Add ability to install the GNOME desktop environment.
Most common global settings (date and time, power management, touchpad settings, theme) can be configured via Ansible variables.
See "group_vars/all" file.
Add ability to install GDM as a graphical login prompt.
Also certain global settings can be changed by Ansible variables. See
"gdm" key of group-vars/all file.
This will be a breaking change for existing users.
After running the new tasks to install and enable LightDM, disable Slim:
# systemctl disable slim.service
LightDM uses `~/.xprofile` instead of `~/.xinitrc`. Move all of the
contents from `~/.xinitrc` to `~/.xprofile`, except for the `exec` line.
In your `~/.xinitrc` you can source your new `~/.xprofile` so that it is
still functional in case you find yourself using it again.
https://wiki.archlinux.org/index.php/Xprofile3a75c5d454
On the next reboot you'll be greeted by LightDM. Slim can then be
uninstalled.
# pacman --remove slim
Hooking into tor's nmtrust config seems to make sense. I don't know if
someone would want to run tor and not this, and you can't run this and
not tor.
This does introduce a new requirement for nmtrust that we haven't seen
before: tor must be started before parcimonie for it to work. Given the
order of the tasks, spark will cause parcimonie to be added to the
trusted unit file after tor, which means we should be good here. But if
a user were to manually edit the file, placing parcimonie above tor, it
would not work. I'm not sure I really want to deal with that problem.
We're running parcimonie for the primary user rather than using the
special `all-users.conf` that parcimonie ships with. That would cause
parcimonie to run for all users who have a ~~/.gnupg`, which in our case
includes root. Running this as root seems like a Bad Idea.
Ansible doesn't seem to have a way to interact with systemd user
instances. All the prep is done, but the user still needs to manually
enable and start the mpd user service.
$ systemd --user enable mpd.service
$ systemd --user start mpd.service
Alternatively, the user could include mpd in their shell profile,
xinitrc, or just call it whenever they want it to run. We jail mpd in
/usr/local/bin, just like everything else.
$ mpd
I don't know if this is the best way to handle building go packages.
Basically the idea is to treat GOPATH like python virtualenvs. A
different one for each thing we install. I'm open to other ideas (or
just moving the root to someplace other than /usr/local/go).
