I updated the Pull Request to submit a new Portfile for openrsync to MacPorts here:
https://github.com/macports/macports-ports/pull/28096#issuecomment-2791744596
I've never done that before, and it's a bit of a weird thing to learn about; but I guess it will suppress warnings in MacPorts for function declarations which it's clueless about (since openrsync has a bunch of things that are OpenBSD specific such as pledge and unveil which macOS doesn't have).
26 files!
One function per line.
In alphabetical order.
But an additional caveat that I learned as I was going through this:
Some of those .list files are symlinks, which confused t.f. out of me at first ("wait, did I already edit that file? No, I did not, but oh, ISEEWHATYOUDIDTHERE").
No doubt there's some sed and or awk that would have been a simpler way to pull the files, alphabetize each line and concatenate them; but I did not feel like doing that kind of scripting at the moment and just dealt with it manually.
https://github.com/macports/macports-ports/pull/28096#issuecomment-2791744596
I've never done that before, and it's a bit of a weird thing to learn about; but I guess it will suppress warnings in MacPorts for function declarations which it's clueless about (since openrsync has a bunch of things that are OpenBSD specific such as pledge and unveil which macOS doesn't have).
26 files!
One function per line.
In alphabetical order.
But an additional caveat that I learned as I was going through this:
Some of those .list files are symlinks, which confused t.f. out of me at first ("wait, did I already edit that file? No, I did not, but oh, ISEEWHATYOUDIDTHERE").
No doubt there's some sed and or awk that would have been a simpler way to pull the files, alphabetize each line and concatenate them; but I did not feel like doing that kind of scripting at the moment and just dealt with it manually.