You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deskflow, which is maintained by folks at Synergy with GPLv2 intact,
Input Leap, which is the actively maintained fork of Barrier.
I believe it is safe to deprecate both synergy and barrier in favor of deskflow, as it has network-level compatibility with both of them. For now, I'm requesting for deskflow since it is arguably more official and I already have a working template that I've been using for quite a while. (It needs an update, though.)
Note that my version of package template requires both #53691 and #53690 to be merged. If that template looks good enough, then I'll go ahead and make a PR. Let me know what you think about deprecating the old, unmaintained packages, though!
Does the requested package meet the package requirements?
Compiled
Is the requested package released?
Yes
The text was updated successfully, but these errors were encountered:
Oops, I should've created this request earlier... (The template was already tested for a couple days when I created the PRs mentioned above.
@classabbyamp If input-leap is to replace barrier, can we have deskflow replace the original synergy? Last time I tried both programs, I had much better Wayland experience with deskflow.
Package name
deskflow
Package homepage
https://deskflow.org/
Description
Deskflow is the official upstream of Synergy.
The current
synergy
package in Void repository is extremely old and no longer actively maintained. Whilebarrier
remained as an alternative, that's no longer true anymore as that project was abandoned with the original maintainer missing.We have two options now:
I believe it is safe to deprecate both
synergy
andbarrier
in favor ofdeskflow
, as it has network-level compatibility with both of them. For now, I'm requesting fordeskflow
since it is arguably more official and I already have a working template that I've been using for quite a while. (It needs an update, though.)Note that my version of package template requires both #53691 and #53690 to be merged. If that template looks good enough, then I'll go ahead and make a PR. Let me know what you think about deprecating the old, unmaintained packages, though!
Does the requested package meet the package requirements?
Compiled
Is the requested package released?
Yes
The text was updated successfully, but these errors were encountered: