| non port: www/node/files/patch-deps_openssl_config_archs_linux-elf_no-asm_openssl-cl.gypi |
|
SVNWeb
|
Number of commits found: 5 |
|
Mon, 30 Jan 2023
|
[ 14:20 Po-Chuan Hsieh (sunpoet)  ]    fa93fdc (Only the first 10 of 85 ports in this commit are shown above.  )
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
|
|
Sat, 23 Oct 2021
|
[ 11:00 Bradley T. Hughes (bhughes) ] f7594b4
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
|
|
Fri, 16 Aug 2019
|
[ 22:27 bhughes ]   (Only the first 10 of 19 ports in this commit are shown above. )
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
|
|
Fri, 8 Feb 2019
|
[ 20:51 bhughes ] (Only the first 10 of 11 ports in this commit are shown above. )
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
|
|
Sun, 13 May 2018
|
[ 08:21 bhughes ]
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>
|
Number of commits found: 5 |
As an Amazon Associate I earn from qualifying purchases.