Starting macchiato here brings down the network connection for a couple
seconds, which will cause subsequent network dependent tasks to fail.
Start the service with a handler after everything else is done.
When we started this project vdirsyncer/khard/khal was a mess of AUR
dependencies that I didn't want to deal with. Everything has official
packages now.
Existing users should remove the old virtualenv and symlinks.
$ sudo rm -r /usr/local/env/pim
$ sudo rm /usr/local/bin/khard
$ sudo rm /usr/local/bin/khal
$ sudo rm /usr/local/bin/vdirsyncer
Both GDM and GNOME uses DConf to manage its own configuration. Extract
the common dependencies into a separate role called "dconf".
DConf provides:
- creating empty directories for configuration
- handler to apply configuration when configuration has changed
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.
I'm using button 12, which on my Elecom HUGE trackball is labeled
"Fn3". Existing users can set this variable to 2 if they wish to retain
the previous behaviour.
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.
Existing users should first stop, disable, and remove the old system timer and service:
$ sudo systemctl stop himawaripy@$USER.timer
$ sudo systemctl disable himawaripy@$USER.timer
$ sudo rm /etc/systemd/system/himawaripy@.*
If the system timer is present in the trusted unit file, remove it.
When this role was created, Ansible did not support systemd user units,
so we setup mailsync as a system service and timer running as the user.
The only practical difference in moving to a user service is that the
user can control the service without sudo, but we might as well.
Existing users should first stop, disable, and remove the old system timer and
service:
$ sudo systemctl stop mailsync@$USER.timer
$ sudo systemctl disable mailsync@$USER.timer
$ sudo rm /etc/systemd/system/mailsync@.*
If the system timer is present in the trusted unit file, remove it.
When this role was created, Ansible did not support sytemd user units,
so we setup git-annex as a system service running as the user. The only
practical difference in moving to a user service is that the user can
control the service without sudo, but we might as well.
Existing users should first stop, disable, and remove the old system
service:
$ sudo systemctl stop git-annex@$USER.service
$ sudo systemctl disable git-annex@$USER.service
$ sudo rm /etc/systemd/system/git-annex@.*
If the system service is present in the trusted unit file, remove it.
