notbugAs an Amazon Associate I earn from qualifying purchases.
Want a good read? Try FreeBSD Mastery: Jails (IT Mastery Book 15)
All times are UTC
Ukraine
non port: www/node/files/patch-deps_openssl_openssl-cl__no__asm.gypi
SVNWeb

Number of commits found: 7

Mon, 30 Jan 2023
[ 14:20 Po-Chuan Hsieh (sunpoet) search for other commits by this committer ]    commit hash:fa93fdc383c190569821ae224413c848c19d9a7c  commit hash:fa93fdc383c190569821ae224413c848c19d9a7c  commit hash:fa93fdc383c190569821ae224413c848c19d9a7c  fa93fdc  (Only the first 10 of 85 ports in this commit are shown above. View all ports for this commit)
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
Fri, 19 Aug 2022
[ 19:53 Joseph Mingrone (jrm) search for other commits by this committer ]    commit hash:c187da08d5688a920e97aa376cccb004cd36faac  commit hash:c187da08d5688a920e97aa376cccb004cd36faac  commit hash:c187da08d5688a920e97aa376cccb004cd36faac  c187da0 
www/node: Update to 18.7.0

https://nodejs.org/en/blog/release/v18.7.0/

Approved by:	bhughes (maintainer, timeout)
Differential Revision:	https://reviews.freebsd.org/D36009

Sponsored by:	The FreeBSD Foundation
Tue, 8 Sep 2020
[ 20:07 bhughes search for other commits by this committer ] Original commit   Revision:548046
www/node: Update 14.9.0 -> 14.10.0

https://nodejs.org/en/blog/release/v14.10.0/

While here, refresh patches with `make makepatch`.

Sponsored by:	Miles AS
Fri, 16 Aug 2019
[ 22:27 bhughes search for other commits by this committer ] Original commit   Revision:509122 (Only the first 10 of 19 ports in this commit are shown above. View all ports for this commit)
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
Wed, 24 Apr 2019
[ 10:55 bhughes search for other commits by this committer ] Original commit   Revision:499831
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
Sun, 13 May 2018
[ 08:21 bhughes search for other commits by this committer ] Original commit   Revision:469781
www/node: fix SSL/TLS on i386

The upgrade to v10.0.0 included significant changes to the OpenSSL
dependency in Node.js, in particular how the build was configured.
Upstream does not include a BSD-x86 config anymore, so the www/node port
ended up using the BSD-x86_64 no-asm config for all builds except x86_64
(which used the asm optimized config). This was a mistake, causing all
32-bit archs to build OpenSSL configured for a 64-bit architecture, and
it causes problems with SSL/TLS as described in PR 228135.

Change the build config to not use BSD-x86_64 no-asm for 32-bit i386 and
arm builds, falling back to the generic linux-elf configuration instead.
Patches remove Linux specific libraries (-ldl) and keep the CFLAGS the
same as the BSD config.

PR:             228135
Reported by:    Marcin Cie\xc5\x9blak <saper@saper.info>
Mon, 30 Apr 2018
[ 22:46 bhughes search for other commits by this committer ] Original commit   Revision:468746 (Only the first 10 of 13 ports in this commit are shown above. View all ports for this commit)
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.

Number of commits found: 7