Date: Fri, 19 Nov 2021 14:53:19 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 259669] comms/xastir: Update to 2.1.8 Message-ID: <bug-259669-7788-98E89drKPM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259669-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-259669-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259669 --- Comment #9 from russo@bogodyn.org --- I was wrong about Xastir's configure expecting gettext. It does probe for = it unnecessarily, but will build fine if it is not present (gettext is not use= d at all even if it's found). So gettext can simply be removed from the USES line. All traces of gettext probing will be removed from Xastir's configure in the next release. Xastir also used to contain a single python script, but that script was rem= oved a couple of releases ago. "python:run" can also be removed from the USES l= ine. My patches do neither of these things. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259669-7788-98E89drKPM>