Hi all,
Jan Staněk <jstanek(a)redhat.com> writes:
Hi all,
the mention on systemd integration in the recent Aleksei's PR [1]
and the related discussion in sway PR [2] got me thinking.
[1]:
https://src.fedoraproject.org/rpms/sway/pull-request/11
[2]:
https://github.com/swaywm/sway/pull/5622#issuecomment-740978176
TL;DR:
What about starting a semi-independent sway-systemd integration project?
Long version:
I get why emersion does not want any init system/display
manager/whatever integrations added to sway itself
– it's more of a maintenance burden,
and it can also be taken as "endorsement" of any given system(s).
On the other hand, leaving the integration instructions on wiki page
and telling distribution packagers to basically implement
any integration "downstream" does not sit well with me.
You would have to extract the snippets from wiki page for each distro
separately, then keep an eye on any changes, etc.
So, I got the idea of starting "unofficial" `sway-systemd` project –
basically extracting the stuff from sway wiki and keeping it in git,
allowing maintainers of other distro packages to pool the efforts.
Unfortunately, I'm not currently planning on actually *using* the
systemd integration in the near future, so I'm probably not the best
person to push that idea further – at least not on my own.
The question is: does this idea is something that appeals to other
people here, and if so, do we want to start the ball rolling?
Yes, I think this is a good idea to have a de-facto upstream for the
systemd config if upstream does not ship systemd config files
themselves. Unfortunately, I don't see myself driving this effort,
nevertheless, I still this is a good way forward.
Cheers,
Dan