[Bug 263090] www/node14: Update to 14.19.3 (includes security fixes)
Date: Thu, 26 May 2022 00:17:09 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263090 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bhughes@freebsd.org Status|New |Open Depends on| |261789 Assignee|bhughes@freebsd.org |ports-bugs@FreeBSD.org See Also| |https://reviews.freebsd.org | |/D35192 Summary|www/node14: Update to |www/node14: Update to |14.19.1 (includes security |14.19.3 (includes security |fixes) [patch] |fixes) Keywords| |needs-qa URL| |https://github.com/nodejs/n | |ode/blob/v14.19.3/doc/chang | |elogs/CHANGELOG_V14.md --- Comment #4 from Kubilay Kocak <koobs@FreeBSD.org> --- ^Triage: Assignee/maintainer timeout (>1 month), open to take. VuXML added via bug 261789 @Derek Given this will be merged to quarterly: - Are there performance implications for the ssl patch to node.gyp? - What is the nature of the COREPACK additional (by default), as it relates to and compares to existing functionality of the ports current version? - Depending on the build system design, CONFIGURE_* options can be non deterministic, and there is no CONFIGURE_ON to match the CONFIGURE_OFF addition here. Did you try COREPACK_CONFIGURE_WITH=corepack? This will set a value in both OPTIONS value cases explicitly, rather than rely on build system defaults. # ${opt}_CONFIGURE_WITH Will add to CONFIGURE_ARGS: # Option enabled --with-${content} # Option disabled --without-${content} Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261789 [Bug 261789] www/node16: Update to 16.14.0 (LTS) -- You are receiving this mail because: You are the assignee for the bug.