From: dataCobra <dataCobra@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rsync: modify to build with rrsync
Date: Sun, 07 Aug 2022 14:30:42 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38518@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
There is a new pull request by dataCobra against master on the void-packages repository
https://github.com/dataCobra/void-packages rsync_template
https://github.com/void-linux/void-packages/pull/38518
rsync: modify to build with rrsync
#### Testing the changes
- I tested the changes in this PR: **YES**, I fully tested the changes before the commit
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64
- aarch64-musl
- armv7l
- armv6l-musl
- x86_x64
- x86_x64-musl
A patch file from https://github.com/void-linux/void-packages/pull/38518.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rsync_template-38518.patch --]
[-- Type: text/x-diff, Size: 1101 bytes --]
From e82bd30c32f607a23c0988a1501eb88e781930bd Mon Sep 17 00:00:00 2001
From: dataCobra <datacobra@thinkbot.de>
Date: Sun, 7 Aug 2022 14:28:29 +0200
Subject: [PATCH] rsync: modify to build with rrsync
---
srcpkgs/rsync/template | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/rsync/template b/srcpkgs/rsync/template
index 2f79c20f8f6b..9563278c7b87 100644
--- a/srcpkgs/rsync/template
+++ b/srcpkgs/rsync/template
@@ -1,10 +1,11 @@
# Template file for 'rsync'
pkgname=rsync
version=3.2.4
-revision=1
+revision=2
build_style=gnu-configure
+configure_args="--with-rrsync"
conf_files="/etc/rsyncd.conf"
-hostmakedepends="perl"
+hostmakedepends="perl python3-commonmark"
makedepends="zlib-devel acl-devel popt-devel xxHash-devel liblz4-devel
openssl-devel libzstd-devel"
short_desc="Remote fast incremental file transfer tool"
@@ -19,7 +20,7 @@ checksum=6f761838d08052b0b6579cf7f6737d93e47f01f4da04c5d24d3447b7f2a5fad1
CFLAGS="-DINET6"
if [ "$CROSS_BUILD" ]; then
- configure_args=" --disable-simd"
+ configure_args+=" --disable-simd"
fi
pre_check() {
next reply other threads:[~2022-08-07 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 12:30 dataCobra [this message]
2022-08-07 12:33 ` dataCobra
2022-08-07 13:30 ` dataCobra
2022-08-08 10:24 ` [PR PATCH] [Merged]: " leahneukirchen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38518@inbox.vuxu.org \
--to=datacobra@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).