1 sway or patterns-sway-sway packages with default branding
this one doesn't have any customization and ppl either already have their own config or would do all the steps documented upstream.
2 sway-openSUSE-branding package
provide custom desktop, target and service files that will cover systemd use case.
For ppl that have DM/Login Manager that supports Wayland sessions.
For those that have tty? Maybe custom script that will run sway with needed vars ?
3 openSUSEway package(or pattern)
full blown OS with preinstalled DE. Will have greetd as login manger that would have custom script to setup envs and start sway as process.
https://bugzilla.suse.com/show_bug.cgi?id=1176195
Now I realize the right way to go.
Use case scenarios:
1 sway or patterns-sway-sway packages with default branding this one doesn't have any customization and ppl either already have their own config or would do all the steps documented upstream.
2 sway-openSUSE-branding package provide custom desktop, target and service files that will cover systemd use case. For ppl that have DM/Login Manager that supports Wayland sessions. For those that have tty? Maybe custom script that will run sway with needed vars ?
3 openSUSEway package(or pattern) full blown OS with preinstalled DE. Will have greetd as login manger that would have custom script to setup envs and start sway as process.