ref(#4554): allow to pick hyprland through dms, do not bundle moving assets.

[h8d13]

This PR removes all bundled assets inside archinstall which belonged upstream: (Discussed here)

It also restores the seat_access choice (which hardcoded polkit).

dms becomes a standalone profile that can orchestrate niri OR hyprland :D

Also removes the dead entry dms-greeter that was removed in upstream https://github.com/AvengeMedia/DankMaterialShell/releases#release-v1.6.0

This as such would break in the current install flow. Currently replaced the default to ly and could be changed if dms-greeter is ever added to extra repos. aims to fix: #4820

---

I do have to note: that the original PR should have been more carefully checked, as its already the 3rd time I go over it and these were kind of obvious issues on how to integrate properly with an installer (probably just happy to add it, but without the after-thoughts).

But kudos to @bbedward for making the changes in his repo, so we can integrate properly.

---

Test: both new profiles under QEMU with GL and vulkan-virtio installed.

[h8d13]

https://gitlab.archlinux.org/archlinux/packaging/packages/dms-shell/-/commit/fd8ca65c63fbb44e78267e7833584c5d66507983

[bbedward]

I agree with replacing with Ly, although maybe we can convince @alerque to bundle dms-greeter in extra?

[h8d13]

As a side note:

I can now integrate mangowm too . (I'm testing this right now) But it seems the logic of your "doctor" reports the service missing even tho it's started through your default config?

From a clanker:

Where it comes from: dms doctor runs checkSystemdServices() (core/cmd/dms/commands_doctor.go). The first-run welcome screen (GreeterDoctorPage.qml) shows the same results, which is probably where you saw it. The check is:
case dmsState.enabled == "disabled":
status, message = statusWarn, "Disabled"
It doesn't look at which compositor is running, and upstream's current master still has the same logic.

• dms setup headless turns off systemd integration for mango (headlessUseSystemd() returns false for it) and writes exec-once=dms run into the config.

---

So I get the warning, but if I enable the service for mango, I then get 2 dms instances ? I'd just remove this from the doctor, since each WM defines how it starts it's service (exec lines or not) or remove the exec lines.

Also captured these warnings at startup (for my OCD aha).