New Portfile work in progress: openrsync help?
grey
artkiver at gmail.com
Tue Apr 8 22:33:03 UTC 2025
Hello!
There was recently an article on undeadly.org about macOS Sequoia
having swapped out rsync (https://rsync.samba.org/) with openrsync
(https://www.openrsync.org) and linking to some additional details
here:
https://derflounder.wordpress.com/2025/04/06/rsync-replaced-with-openrsync-on-macos-sequoia/
A while ago, I had looked into making a Portfile for openrsync, but I
couldn't get it to build cleanly on macOS at the time and kind of
forgot about it.
Whereas with that recent news, I got the feeling that openrsync might
be worth revisiting and Stefan Sperling (stsp@ another OpenBSD
developer) pointed out https://github.com/kristapsdz/openrsync which
has Kristaps' openrsync from OpenBSD + some portability improvements
and low and behold, unlike before I was able to get openrsync to build
cleanly on macOS!
I've run into an issue with my MacPorts Portfile efforts to share that good
news with MacPorts users though insomuch as openrsync uses Kristaps'
oconfigure (https://github.com/kristapsdz/oconfigure) which expects
the prefix parameter to be passed as follows:
./configure PREFIX=/opt/local
Whereas MacPorts defaults to:
./configure --prefix=/opt/local
Which causes oconfigure to throw the following error.
"./configure: invalid key: --prefix"
I opened a Trac issue (https://trac.macports.org/ticket/72311)
documenting my efforts thus far (as well as a partial attempt at
creating a Portfile for oconfigure, thinking that might be another way
to move this along) but I think the TL;DR I have
is:
Is there a way to get MacPorts to be a bit less hand holding with
--prefix and instead respect configure.args more explicitly?
Because my attempts to rectify the build within MacPorts by adding:
configure.args PREFIX=${prefix}
While it does correctly pass PREFIX=/opt/local to ./configure as works
when building locally, still also tries to pass --prefix=/opt/local
which will still result in an "invalid key: --prefix" error from
openrsync's use of oconfigure.
I feel as if it's *so close* but I am missing something obvious, so
hopefully someone else can help with something I am missing?
Thanks!
|
グ
レ
ェ
ーgrey
More information about the macports-dev
mailing list