systemd integration repository

[Jan Staněk]

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?

Have a nice day!
-- 
Jan Staněk
Software Engineer, Red Hat
jstanek(a)redhat.com   irc: jstanek

[Dan Čermák]

Hi all,

Jan Staněk <jstanek(a)redhat.com&gt; 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

[Aleksei Bavshin]

Hi Jan, all,

On 1/28/21 4:48 AM, Jan Staněk wrote:
>  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? 
(mostly rehashing my comment from the PR)

I moved all the systemd bits from the PR to a new repository[1] with 
expanded comments and added my script to deal with 
Changes/EnableSystemdOomd[2].


The cgroups script may also be of interest for i3 SIG as I confirmed 
that it works with i3 as long as the correct DBUS_SESSION_BUS_ADDRESS is 
provided.

The new `sway-systemd` package is available from my sway-extras copr[3].
Systemd-oomd script is only installed for f34+ though, so rebuild the 
package from git repo with `rpkg --path srpm local --with cgroups` if 
you want to test that part on f33.

The current plan is to make sure that the code works, submit the package 
to Fedora and add `Recommends: sway-systemd` to the `sway.spec`. 
Inviting other distributions' maintainers to participate is also an 
important part of the plan.

Code reviews and testing would be appreciated!

[1] https://github.com/alebastr/sway-systemd
[2] https://fedoraproject.org/wiki/Changes/EnableSystemdOomd
[3] 
https://copr.fedorainfracloud.org/coprs/alebastr/sway-extras/package/sway...

-- 
With best regards,
Aleksei Bavshin