Date: Tue, 12 Jul 2022 21:43:34 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 265180] www/chromium: actually use the system-installed ICU Message-ID: <bug-265180-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265180 Bug ID: 265180 Summary: www/chromium: actually use the system-installed ICU Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: mi@ALDAN.algebra.com Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) Created attachment 235226 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D235226&action= =3Dedit Use the already-installed ICU Though the port lists devel/icu among the LIB_DEPENDS, the upstream code bu= ilds the bundled version of ICU anyway... This is true about a number of other bundled components too (AOM, AVIF, jsoncpp, node, v8, etc.), but ICU seems to be the easiest to fix. The proposed patch adds ICU to the existing (incomplete) list of possible dependencies, and, additionally, ensures, the icu/source folder is never ev= en extracted from the tarball. For good measure... The post-patch gymnastics are only necessary because of the is_official_build=3Dtrue setting -- do we really need it? --=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-265180-7788>