void-linux / void-linux/void-packages
Package request: Deskflow
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Package name
deskflow
Package homepage
Description
Deskflow is the official upstream of Synergy.
The current synergy package in Void repository is extremely old and no longer actively maintained. While barrier 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:
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked deskflow template and the existing srcpkgs/synergy/template and srcpkgs/barrier/template files. Check the status and requirements of #53691 and #53690, then update the template as needed. Done means a working Deskflow package template is ready for a pull request, with any deprecation decision for synergy and barrier addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100