@Sabu Because Syncthing Tray depends on Boost which breaks its ABI on every release. That's generally a good thing as it allows for a better evolution of that library and users don't need to care about it - only developers/distributors. As an AUR "user" you are unfortunately put into the role of a distributor by having to build packages yourself. Even if using my binary repo this is problematic because there will always be a small delay between official repos and me catching up with them.
I could mitigate this by linking statically against Boost but this would go against the usual packaging practices.
Pinned Comments
Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2025-05-03 08:48 (UTC) by Martchus)
All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
There also exist a binary repository: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff
Important remarks:
pkgrel
of the AUR package when a rebuild is required (only in accordance with Arch Linux of course, not in accordance with Manjaro).syncthingtray
broken until it has been rebuilt) or to uninstallsyncthingtray
temporarily before the update. After the updatesyncthingtray
can be rebuilt and reinstalled again.makechrootpkg
which is also how official developers build their packages (and how packages in my binary repository are built).c++utilities
,qtutilities
,qtforkawesome
andsyncthingtray
in that order.syncthingtray-qt6
instead of this package.makepkg --nocheck
ormakechrootpkg -- --nocheck
. It makes still sense to report failures. But please include the actual error message and not just the last few lines.