Marty Oehme
996560410e
This should allow just having a general 'target' system for ansible which will take all the modifications - but not care whether we connect to it locally (i.e. running from void) or through chroot. We can set the connection method for the specific system(s) in whatever we group as part of the target group then. For local installation we simply add locally connected hosts and for chroot set up chrooted hosts.
33 lines
878 B
YAML
33 lines
878 B
YAML
- name: Install void wayland environment
|
|
hosts: target_system
|
|
become: true
|
|
tasks:
|
|
- name: Install intel wayland drivers
|
|
community.general.xbps:
|
|
name:
|
|
- mesa-dri
|
|
state: present
|
|
|
|
- name: Install wayland packages
|
|
community.general.xbps:
|
|
name:
|
|
- dbus
|
|
- seatd
|
|
- turnstile
|
|
state: present
|
|
# notify: installed-wayland -> TODO: Use handler? Currently using task below
|
|
|
|
- name: Activate wayland services
|
|
ansible.builtin.file:
|
|
force: "yes"
|
|
src: "/etc/sv/{{ item }}"
|
|
dest: "/etc/runit/runsvdir/default/{{ item }}"
|
|
state: link
|
|
with_items: [dbus, turnstiled, seatd]
|
|
|
|
- name: Install wlr desktop portals
|
|
community.general.xbps:
|
|
name:
|
|
- xdg-desktop-portal
|
|
- xdg-desktop-portal-wlr
|
|
state: present
|