Node.js is a JavaScript runtime built on Chrome's V8 JavaScript
engine. Node.js uses an event-driven, non-blocking I/O model that
makes it lightweight and efficient. Node.js' package ecosystem,
npm, is the largest ecosystem of open source libraries in the world.
===> The following configuration options are available for node16-16.20.1_3:
BUNDLED_SSL=off: Use node.js's bundled OpenSSL implementation
COREPACK=on: Build and install corepack package manager
DOCS=on: Build and/or install documentation
NLS=on: Native Language Support
===> Use 'make config' to modify these settings
www/node16: Remove DTrace support to fix build with upcoming binutils 2.41
* With binutils 2.41 build fails as following.
LD_LIBRARY_PATH=/wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/lib.host:/wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/lib.target:$LD_LIBRARY_PATH;
export LD_LIBRARY_PATH; cd ../.; mkdir -p
/wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj.target/libnode/src;
dtrace -64
"-I/wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj/gen" -Isrc
-C -G -s src/v8ustack.d -o
"/wrkdirs/usr/ports/www/node16/work/node-v16.20.1/out/Release/obj.target/libnode/src/node_dtrace_ustack.o"
dtrace: failed to compile script src/v8ustack.d: line 1: failed to resolve
V8DBG_SMITAG: Unknown variable name
* This is because behaviour of objdump has changes with binutils 2.41. [1][2]
* On upstream DTrace support itself has been removed with Node.js 19.x.
* There is a pull request that says it fixes build error. [3] I tried
it but unfortunately it doesn't work as is expected.
* Upstream suggests me to remove DTrace support. [4]
Reference: https://github.com/nodejs/node/issues/49991#issue-1920717730 [1]
Reference: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=0a3137ce4c4b38ee8
[2]
Reference: https://github.com/nodejs/node/pull/49992 [3]
Reference: https://github.com/nodejs/node/pull/49992#issuecomment-1784231190 [4]
PR: 274846
Approved by: maintainer timeout
www/node16: Mark DEPRECATED
nodejs comunity has decided to change the End-of-life date to match the
end of life date of OpenSSL 1.1.1 which is on 2023-09-11. Based on that
mark this port DEPRECATED and set to expire by the end of this quarterly
on 2023-09-30.
See also:
https://nodejs.org/en/blog/announcements/nodejs16-eol
Approved by: portmgr (blanket)
*/*: Fix build with llvm16 on 13.2-STABLE
As like as HEAD(14.0-RELEASE) llvm16 was merged in base for 13.2-STABLE
with the OSVERSION 1302507.
- Utilize USE_CXXSTD=c++14 or similar solution where applicable
- Update conditionals to addtionally check for OSVERSION greater than
1302507 and less than 1400000
Approved by: portmgr (blanket)
Sponsored by: The FreeBSD Foundation
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
www/node16: Fix build with OpenSSL 3
- This was tested only with OpenSSL 3 from base but not with openssl30
or openssl31 ports.
- Regen patches
PR: 271656
www/node16: Update to 16.19.1 and use ccache if available
- Update to 16.19.1
- Set CC_host and CXX_host to also use ccache when available. This helps
to speed up the build significantly.
And while here, also portclippy/portfmt a bit.
PR: 269491
www/node16: Use ccache if available
Set CC_host and CXX_host to also use ccache when available. This helps
to speed up the build significantly.
And while here, also portclippy/portfmt a bit.
PR: 269491
Framework: Rewrite nodejs.mk and reorganize www/{node,npm,yarn}
The current USES=nodejs has the following issues:
- www/node is not the default version while www/node16 is.
- It also means inconsistent naming of node ports.
- www/npm duplicates with www/npm-node16.
- www/yarn duplicates with www/yarn-node16.
The notable changes are introduced to fix the above issues:
- Rewrite Mk/Uses/nodejs.mk.
- Add new LTS version of nodejs (www/noe18).
- Add new current version of nodejs (www/node19).
- Change default nodejs version from 16 to 18 (latest LTS).
- Use consistent naming for all supported node versions.
- Convert www/node, www/npm and www/yarn to meta ports.
After this commit:
- All supported node versions are named as node{14,16,18,19}
- www/node is a meta port which depends on the default version (e.g. www/node18)
- www/npm is a meta port which depends on the default version (e.g.
www/npm-node18)
- www/yarn is a meta port which depends on the default version (e.g.
www/yarn-node18)
- Bump PORTREVISION of dependent ports for dependency change (from www/node16 to
www/node18)
Discussed with: jrm, otis, pizzamig
www/node16: Update to 16.18.1
The following CVE is fixed in this release:
CVE-2022-43548: DNS rebinding in --inspect via invalid octal IP
address (Medium)
Changelog: https://github.com/nodejs/node/releases/tag/v16.18.1
www/node16: Security update to 16.17.1
Changelog: https://github.com/nodejs/node/releases/tag/v16.17.1
The following CVEs are fixed in this release:
CVE-2022-32212: DNS rebinding in --inspect on macOS
CVE-2022-32213: bypass via obs-fold mechanic
CVE-2022-35255: Weak randomness in WebCrypto keygen
CVE-2022-35256: HTTP Request Smuggling - Incorrect Parsing of Header Fields
PR: 266595
Approved by: (maintainer timeout)
MFH: 2022Q4
Differential Revision: https://reviews.freebsd.org/D36692
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
*/*: Remove redundant '-[0-9]*' from CONFLICTS_INSTALL
The conflict checks compare the patterns first against the package
names without version (as reported by "pkg query "%n"), then - if
there was no match - agsinst the full package names including the
version (as reported by "pkg query "%n-%v").
Approved by: portmgr (blanket)
www/node16: Update 16.12.0_1 -> 16.13.0
This release marks the transition of Node.js 16.x into Long Term Support
(LTS) with the codename 'Gallium'. The 16.x release line now moves into
"Active LTS" and will remain so until October 2022. After that time, it
will move into "Maintenance" until end of life in April 2024.
https://nodejs.org/en/blog/release/v16.13.0/
While here, fix the pkg-plist to allow building www/node16 with the
BUNDLED_SSL option enabled.
MFH: 2021Q4
Sponsored by: Miles AS
www/node16: copy from www/node, update 16.11.1 -> 16.12.0
Create a new port for the latest Node.js v16.x release, which will
become the v16.x LTS release line. Update CONFLICTS for the existing
Node.js ports to include the new node16 port and remove non-existent ports.
https://nodejs.org/en/blog/release/v16.12.0/
MFH: 2021Q4
Sponsored by: Miles AS
