From: Chad Dougherty <crd@acm.org>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Jari Aalto <jari.aalto@cante.net>
Subject: Re: [ITP] rsync 3.2.6
Date: Tue, 25 Oct 2022 20:44:08 -0400 [thread overview]
Message-ID: <dcc27450-d200-4069-80f8-28b36d57e70a@acm.org> (raw)
In-Reply-To: <c9f62b84-f1bf-e14a-5837-1c42364e5dd3@dronecode.org.uk>
On 2022-10-09 10:23, Jon Turney wrote:
> Thanks for looking into updating this. I'd like to give the existing
> maintainer first refusal, though.
>
Any new thoughts on this?
There was a new upstream release, rsync-3.2.7, and I've updated my
cygport and its associated artifacts:
https://github.com/crd477/cygports/tree/main/rsync
>> # Enable this function for releases that work without autoreconf
>> src_compile()
>
> You should only override the default src_compile if it doesn't work.
>
> The fact that autoreconf isn't apparently necessary, doesn't mean it
> should be omitted, since that means that future fixes to the
> autoconfiguration machinery aren't automatically incorporated into the
> package, but will only appear when upstream updates the autotools used
> to generate the distributed autoconfiguration files.
>
OK, got it. My current cygport no longer skips the cygautoreconf step.
Thanks...
--
-Chad
next prev parent reply other threads:[~2022-10-26 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 1:29 Chad Dougherty
2022-10-06 17:24 ` Adam Dinwoodie
2022-10-06 18:20 ` Chad Dougherty
2022-10-06 20:01 ` Ken Brown
2022-10-09 14:23 ` Jon Turney
2022-10-09 21:18 ` Brian Inglis
2022-10-10 0:28 ` Chad Dougherty
2022-10-10 7:15 ` ASSI
2022-10-26 0:44 ` Chad Dougherty [this message]
2022-12-02 15:07 ` Jon Turney
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=dcc27450-d200-4069-80f8-28b36d57e70a@acm.org \
--to=crd@acm.org \
--cc=cygwin-apps@cygwin.com \
--cc=jari.aalto@cante.net \
--cc=jon.turney@dronecode.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).