14:20 Po-Chuan Hsieh (sunpoet) 

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

    fa93fdc

11:00 Bradley T. Hughes (bhughes) 

www/node: Update 16.11.1 -> 17.0.0

Upgrade to the latest major vesrion of Node.js. Regenerate patches
since some have been adopted upstream, while others needed refreshing.

https://nodejs.org/en/blog/release/v17.0.0/

MFH:		2021Q4
Sponsored by:   Miles AS

    f7594b4

19:02 bhughes 

www/node: Update 15.10.0 -> 15.11.0

https://nodejs.org/en/blog/release/v15.11.0/

Sponsored by:	Miles AS

 

10:52 bhughes 

www/node: Update 15.7.0 -> 15.8.0

https://nodejs.org/en/blog/release/v15.8.0/

Regenerate patches with `make makepatch` and re-introduce the
dependency on dns/c-ares now that it is at version 1.17.1 (the
minimum required version for Node.js).

Sponsored by:	Miles AS

 

21:32 bhughes 

www/node: Update 14.14.0 -> 15.0.0

Update to the latest major release of Node.js, which includes many
significant changes. Users are encouraged to read the release notes
before upgrading.

https://nodejs.org/en/blog/release/v15.0.0/

While here, refresh existing patches with `make makepatch`, removing
some powerpc* related patches that have been adopted/reworked upstream
in V8.

Remove the dependency on dns/c-ares and use the bundled version
instead, since Node.js has adopted a change to c-ares that has not yet
been released. The dependency will be re-added once dns/c-ares has
been updated to a release that contains support for CAA DNS records.

An UPDATING entry has also been added to include a notice about this
major version upgrade, and steps users can take to continue using the
v14.x line, which is now LTS.

Sponsored by:	Miles AS

 

22:45 bhughes 

www/node: Update 13.9.0 -> 13.10.1

https://nodejs.org/en/blog/release/v13.10.0/
https://nodejs.org/en/blog/release/v13.10.1/

Refresh patches with `make makepatch`.

Sponsored by:	Miles AS

 

22:26 bhughes 

www/node: Update 13.5.0 -> 13.6.0

https://nodejs.org/en/blog/release/v13.6.0/

While here, regenerate patches with `make makepatch`.

Sponsored by:	Miles AS

 

21:45 bhughes 

www/node: Update 13.4.0 -> 13.5.0

https://nodejs.org/en/blog/release/v13.5.0/

While here, bump the minimum dependency on libuv and regenerate patches
with `make makepatch`.

Sponsored by:	Miles AS

 

22:38 bhughes 

www/node: Update 12.13.0 -> 13.0.0

Update to the latest major release of Node.js, regenerating patches
with `make makepatch` while here.

https://nodejs.org/en/blog/release/v13.0.0/

Sponsored by:	Miles AS

 

15:50 bhughes 

www/node: Update 12.12.0 -> 12.13.0

Update to the latest LTS release of Node.js. Regenerate patches with
`make makepatch`.

https://nodejs.org/en/blog/release/v12.13.0/

Sponsored by:	Miles AS

 

20:08 bhughes 

www/node: Update 12.8.1 -> 12.9.0

https://nodejs.org/en/blog/release/v12.9.0/

Regenerate patches with `make makepatch`, taking care to keep patches
for files that have moved after Node.js upgraded the bundled V8
dependency.

Sponsored by:	Miles AS

 

22:27 bhughes 

www/node: Update 12.7.0 -> 12.8.0

https://nodejs.org/en/blog/release/v12.8.0/

The bundled OpenSSL configuration now includes BSD-x86, which this port
can now use. The build for i386 is still using the no-asm variant for
the time being. Assembler errors in BSD-x86/asm-avx2 need to be
investigated to be able to enable asm with the bundled OpenSSL.

While here, regenerate all remaining patches with `make makepatch`.

Sponsored by:	Miles AS

 

10:55 bhughes 

www/node: Update 11.14.0 -> 12.0.0

Update to the latest major release of Node.js, which includes many
significant changes. Users are encouraced to read the release
announcement before upgrading.

https://nodejs.org/en/blog/release/v12.0.0/

Update minimum version requirements for dependencies. Regenerate patches
with `make makepatch`.

Sponsored by:	Miles AS

 

20:51 bhughes 

www/node: Update 11.8.0 -> 11.9.0

Update patches and pkg-plist for deps/openssl/**/* after upstream
pdated to OpenSSL 1.1.1a and refresh existing patches with
`make makepatch`.

https://nodejs.org/en/blog/release/v11.9.0/

Sponsored by:	Miles AS

 

22:09 bhughes 

www/node: Update 10.12.0_1 -> 11.0.0

Update to the latest major release of Node.js. Upstream has dropped
support for FreeBSD 10.x, so mark the port as BROKEN on FreeBSD 10.
Regenerate patches with `make makepatch`.

https://nodejs.org/en/blog/release/v11.0.0/

Sponsored by:	Miles AS

 

18:43 bhughes 

www/node: Update 10.3.0 -> 10.4.0

https://nodejs.org/en/blog/release/v10.4.0/

Remove files/patch-deps_v8_src_base_cpu.cc, which has been applied
upstream and is no longer necessary (as reported in PR 228779). Other
patches have been refreshed as needed with `make makepatch`.

PR:		228779
Reported by:	Sylvain Garrigues <sylvain@sylvaingarrigues.com>
Sponsored by:	Miles AS

 

22:46 bhughes 

www/node: Update 9.11.1_1 -> 10.0.0

Update to the latest major release of Node.js. This release includes
many significant changes, both to Node.js itself and the FreeBSD port.

https://nodejs.org/en/blog/release/v10.0.0/

In particular, Node.js now requires OpenSSL 1.1.0h, so the BUNDLED_SSL
option is enabled by default. It is still possible to disable this
option when using security/openssl-devel (which is currently at 1.1.0h).
Multiple patches are required to get Node.js building with the bundled
OpenSSL library. Only amd64 builds get optimized assembler; all other
archs use non-asm implementations.