Symless has updated Synergy and posted a warning that Synergy 1.x is not compatible with Synergy 2.x. Request a rev bump and a warning added for the following:
The bug has been referenced in the following commit(s):
Author: Andreas Sturmlechner <email@example.com>
AuthorDate: 2018-05-11 21:57:30 +0000
Commit: Andreas Sturmlechner <firstname.lastname@example.org>
CommitDate: 2018-05-12 11:21:20 +0000
x11-misc/synergy: 1.9.1 version bump, Qt4 -> Qt5
Package-Manager: Portage-2.3.36, Repoman-2.3.9
x11-misc/synergy/Manifest | 1 +
.../files/synergy-1.9.1-cmake-version.patch | 57 ++++++++++++
x11-misc/synergy/files/synergy-1.9.1-gtest.patch | 28 ++++++
.../files/synergy-1.9.1-internal-gmock-gtest.patch | 23 +++++
x11-misc/synergy/files/synergy-1.9.1-pthread.patch | 11 +++
x11-misc/synergy/files/synergy-1.9.1-qt-5.11.patch | 31 +++++++
x11-misc/synergy/synergy-1.9.1.ebuild | 103 +++++++++++++++++++++
7 files changed, 254 insertions(+)
The latest version is 2.0.12_beta from 2018-06-22 and there has been no release of the 2.0 series since then: https://github.com/symless/synergy-core/releases
Also note that it appears as if *all* the 2.0 versions are supposed to be beta versions. Symless is still selling version 1 on their website and in the forums  Kelvin Tran (Moderator) says that "Synergy 2 has been deprecated. A new "major version" ([...] Synergy 3) will be coming in the next few years". Nick Bolton, CEO of Symless, replies: "We're working on the next major version, and it'll probably take about 3 years more to complete. We plan on releasing an early alpha in Q1 of 2020".
Thus I propose to remove the 2.0 versions from Gentoo, since they are not supported upstream.
I just found the official announcement from 2018-05-24: https://symless.com/blog/synergy-2-back-beta
In their support section they recommend people to downgrade to version 1: https://symless.com/help/articles/synergy-2-is-a-beta
Created attachment 674233 [details]
synergy v1.11.1 ebuild
Here is a updated version for synergy which increases it to 1.11.1 the latest working version for tar archives. Upstream recently moved towards git submodules which will require a rewrite of the ebuild, which I'm not capable of doing so far as this is my first ebuild 'modification'.
I'm not entirely sure that the qt patches are needed either as I have the QT5 use flag enabled, and everything works without the patch file. This includes all Pro features as well.
I also recommend removal of all v2.x ebuilds as all development is on the v1 branch.
ps; if there is something else needed please let me know as this is my first ebuild/patch.
I'm surprised about the incompatibility claim -- I just happen to be running some old 1.x on Windows with 2.0.0 server on Linux. But I clearly see that it's been discontinued, so the plan is to:
1. Stabilize the current 1.x version (only 2.0.0 is stable now).
2. Mask >=2.0.0 for removal.
3. Bump 1.x.
Ideally, I'd like to get tests to work in the current 1.x version but between ugly code upstream and Gentoo patches, this seems non-trivial.
The bug has been closed via the following commit(s):
Author: Michał Górny <email@example.com>
AuthorDate: 2020-11-30 09:52:26 +0000
Commit: Michał Górny <firstname.lastname@example.org>
CommitDate: 2020-11-30 09:55:38 +0000
x11-misc/synergy: Bump to 1.12.0
Signed-off-by: Michał Górny <email@example.com>
x11-misc/synergy/Manifest | 3 +
x11-misc/synergy/synergy-1.12.0.ebuild | 114 +++++++++++++++++++++++++++++++++
2 files changed, 117 insertions(+)