Date: Tue, 12 Jul 2022 21:43:34 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: maintainer-feedback requested: [Bug 265180] www/chromium: actually use the system-installed ICU Message-ID: <bug-265180-28929-OnuNkhQJGZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-265180-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-265180-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-chromium (Nobo= dy) <chromium@FreeBSD.org> for maintainer-feedback: Bug 265180: www/chromium: actually use the system-installed ICU https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D265180 --- Description --- 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-265180-28929-OnuNkhQJGZ>