Hello Jason, I emailed to you a revisioned pkgbuild on 2023/07/10 but haven't heard back, main changes:
- proper use of source_$CARCH=()
- download and install current manpages (the ones uploaded here are from 2014)
pkgbuild now uploaded for all
Git Clone URL: | https://aur.archlinux.org/syncthing-bin.git (read-only, click to copy) |
---|---|
Package Base: | syncthing-bin |
Description: | Open Source Continuous Replication / Cluster Synchronization Thing: binary. |
Upstream URL: | https://syncthing.net/ |
Licenses: | MPL2 |
Conflicts: | syncthing |
Provides: | syncthing |
Submitter: | jasonwryan |
Maintainer: | jasonwryan |
Last Packager: | jasonwryan |
Votes: | 29 |
Popularity: | 0.000000 |
First Submitted: | 2014-08-26 08:54 (UTC) |
Last Updated: | 2024-10-16 20:06 (UTC) |
Hello Jason, I emailed to you a revisioned pkgbuild on 2023/07/10 but haven't heard back, main changes:
pkgbuild now uploaded for all
@bt90 - I'll add them to the next release. Thanks!
Can we also package the upstream sysctl config file?
install -D -m 644 "etc/linux-sysctl/30-${_realname}.conf" \
"${pkgdir}/usr/lib/sysctl.d/30-${_realname}.conf"
Edit: maybe also the ufw preset?
install -D -m 644 "etc/firewall-ufw/${_realname}" \
"${pkgdir}/etc/ufw/applications.d/ufw-${_realname}"
@jonathon - this has been discussed on aur-general: this package is for those of us that don't want to install go for one package.
This package proved to be very useful for me, I'm still using it, as this seems to be more stable than the compiled one in the repos: https://bbs.archlinux.org/viewtopic.php?id=254862
The syncthing package in community is a recent inclusion. This AUR package existed as a way to install the binary distribution from upstream directly. I guess now that syncthing is in community this package is less useful, provided that the repo version is kept up to date. At this time, the package in community is one version behind upstream.
What does this package provide that's different to syncthing
in community?
From https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submission, "The submitted PKGBUILDs must not build applications already in any of the official binary repositories under any circumstances... Exception to this strict rule may only be packages having extra features enabled and/or patches in comparison to the official ones."
Update to the case
statement in PKGBUILD
to support ARM64 (tested this on a Raspberry Pi4 running Manjaro aarch64).
aarch64) _pkgarch="arm64"
sha256sums+=('e685175c382995fe86b024b77ede909cbc07e5a3c99996f040f0820effc90174')
;;
Thanks.
It seems you used the SHA256 sum of the arm64 archive for 1.9.0. I'm pretty sure it used to be the sum of the arm archive.
Pinned Comments
jasonwryan commented on 2019-06-03 01:41 (UTC)
Jakob generally takes a day or two to upload the hash file after each release. Please don't flag the package out-of-date until after he has published that file...