Package Details: synergy-1.6 1.6.3-2

Git Clone URL: https://aur.archlinux.org/synergy-1.6.git (read-only, click to copy)
Package Base: synergy-1.6
Description: Synergy upstream 1.6 branch. 1.7.x is very unstable on Linux.
Upstream URL: http://synergy-foss.org
Licenses: GPL2
Conflicts: synergy
Provides: synergy
Submitter: flavi0
Maintainer: None
Last Packager: xiota
Votes: 12
Popularity: 0.000000
First Submitted: 2015-08-12 16:42 (UTC)
Last Updated: 2022-09-16 05:16 (UTC)

Latest Comments

1 2 Next › Last »

alxhoff commented on 2019-01-25 16:07 (UTC)

new md5 for the zip (replace the top line in the PKGBUILD checksums)

fa536233ecb331bab4b63389baff257c5a234f0d67cd3a543e19ef89ee5f3fbbf5142aba11035e2fa9e6a3629b5df491e6987abe8ab0cbfa3795b5e78c852785

danieltimlee commented on 2017-12-03 16:50 (UTC)

The github repository name has been changed to 'synergy-core' from 'synergy'

Due to this change, An easy way to build this synergy-1.6 is, just

  1. fork synergy git to your repo
  2. change repo name from 'synergy-core' -> 'synergy'
  3. edit PKGBUILD's synergy url to your repo. [edit with yaourt (or any PKGBUILD editable package manager)]

NhaMeh commented on 2017-11-24 03:12 (UTC)

When using the zip suggested by Beacon515L I had to also change the directoryname at line 33, 46, and 61 to "$_pkgname-core-1.6.3-final". The "-core" part seems new and is in line with the URL change. The checksum for the zip file is 2cb723b8bd446268a8fab9b9a253881241f19523a850a4d8ffc09ce3b0caebddc3063161880cb67ae959c97610eb5826bc09f283cd664f0393d5c9e56fc1df9c

jose1711 commented on 2017-11-15 11:05 (UTC)

i think it makes sense to put .service files into /usr/lib/systemd/user/ (same as synergy package has it) so that a user can do systemctl --user start/enable synergys.

Beacon515L commented on 2017-10-09 12:34 (UTC)

The release tarball is now at https://github.com/symless/synergy-core/archive/1.6.3-final.zip

account60217652 commented on 2017-09-18 15:18 (UTC)

curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading https://github.com/symless/synergy/archive/1.6.3-final.tar.gz Aborting...

visibilityspots commented on 2017-05-30 11:02 (UTC)

Could you add the armv7h architecture to the PKGBUILD file? I just installed it on a raspberry pi and it works fine.

flavi0 commented on 2016-06-06 23:21 (UTC)

I added a patch which declares the destructor in question as noexcept(false). This is strictly speaking just as wrong as before, since destructors should never throw in C++ (see e.g. http://www.gotw.ca/gotw/047.htm). However I guess this will not be addressed upstream anymore, since it's actually a libcryptopp issue and I assume devs won't bother updating the 1.6.3 dependency since there's lots of pending work for 1.7. For completeness, this was not just an issue of more warnings being emitted, g++ 6 defaults to -std=g++14, and in C++11 destructors are implicitly declared noexcept. @samueldr Thanks for reporting!

samueldr commented on 2016-05-21 18:32 (UTC)

The recent updates to gcc probably added more warnings, as the default build now terminates with: .../synergy-1.6/src/synergy-1.6.3-final/src/lib/io/../../../ext/cryptopp562/algparam.h:277:34: error: throw will always call terminate() [-Werror=terminate] throw ParameterNotUsed(m_name); Since this was previously "fine" with earlier versions of the compiler, bypassing the warning should be fine, maybe. The error should be fixed "upstream", but this would entail doing more work, and probably understanding the codebase. For a quick fix, compilation can be changed to not treat warnings as error, just before the call to cmake: sed -i'' 's/-Werror//' CMakeLists.txt Or as a patch: --- a/PKGBUILD 2016-05-21 14:26:41.618115277 -0400 +++ b/PKGBUILD 2016-05-21 14:19:42.132744548 -0400 @@ -43,6 +43,7 @@ build() { cd $_pkgname-1.6.3-final + sed -i'' 's/-Werror//' CMakeLists.txt cmake -DCMAKE_INSTALL_PREFIX=/usr . make (Alternatively, and a better alternative, would be to find out how to treat all warnings as error, except for -Werror=terminate.)

flavi0 commented on 2016-02-23 09:43 (UTC) (edited on 2016-02-23 09:43 (UTC) by flavi0)

@bldewolf: thanks for notification, updated!

1 2 Next › Last »