FileZilla: current version requires SDK 11
Mark Anderson
mark at macports.org
Sun Feb 7 00:02:53 UTC 2021
I would maybe have one of us try it for 11.0 and if < 11 is detected the
latest pre macOS 11 build is done. I do that for iTerm - i have had some
problems recently but it mostly worked.
—Mark
On Sat, Feb 6, 2021 at 12:55 PM Lothar Haeger <lothar.haeger at gmx.net> wrote:
> The latest version of FileZilla fails to build on my Catalina system and
> the developer states, it requires the latest BigSur SDK to compile (though
> the final binary should be running on macOS 10.11 and newer):
>
> → https://trac.filezilla-project.org/ticket/12358
>
> If I understand that correctly, MacPorts will only be able to build the
> software on BigSur, right? Since I am not yet on BigSur and do not intend
> to go there anytime soon, how to best approach this kind of issue?
>
> - I could drop maintainership and hope for someone running BigSur to pick
> it up.
> - I could patch the source and try to revert any use of the latest code
> changes that now require SDK 11.
> - I could just ignore updates form now on and MacPorts stays on the
> current version forever.
> - I could turn this into a (partially) binary port ;-)
>
> Any suggestions? Is there any simple solution I'm overlooking?
--
Sent from Gmail Mobile on iPhone
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20210206/ead6e0d6/attachment.htm>
More information about the macports-dev
mailing list