linux/meta-openembedded.git/meta-oe/recipes-devtools/nodejs, branch krogoth-next

nodejs: update to 4.4.3

2016-05-02T21:03:02+00:00

LICENSE checksum has changed due to OpenSSL copyright year being bumped from 1998-2011 to 1998-2016. Signed-off-by: Jonathan Liu Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

nodejs: update to 4.4.2

2016-05-02T21:03:00+00:00

Signed-off-by: Jonathan Liu Signed-off-by: Martin Jansa Signed-off-by: Armin Kuster

nodejs: update to 4.4.1

2016-03-25T10:27:30+00:00

Signed-off-by: Jonathan Liu Signed-off-by: Martin Jansa

nodejs: update to 4.4.0

2016-03-25T10:26:57+00:00

LICENSE checksum has changed to fix a small error in the URL for the npm public registry, changing the URL from "https://registry.npmjs.com" to "https://registry.npmjs.org". Signed-off-by: Jonathan Liu Signed-off-by: Martin Jansa

nodejs: update to 4.3.2

2016-03-04T08:06:08+00:00

Signed-off-by: Jonathan Liu Signed-off-by: Martin Jansa

nodejs: update to 4.3.1

2016-03-01T23:03:18+00:00

Fixes CVE-2016-2086 and CVE-2016-2216. LICENSE checksum changed because it was regenerated using the new tools/license-builder.sh script but the licensing remains the same. Signed-off-by: Jonathan Liu Signed-off-by: Martin Jansa

nodejs: upgrade from 4.2.4 to 4.2.6

2016-02-15T09:15:26+00:00

...plus a switch to xz. Signed-off-by: Trevor Woerner Signed-off-by: Martin Jansa

nodejs: update from 4.2.3 to 4.2.4

2016-01-27T11:36:31+00:00

Additionally, the LICENSE file changed as follows: - npm is a package manager program located at deps/npm. npm's license follows: """ - Copyright (c) Isaac Z. Schlueter - All rights reserved. - - npm is released under the Artistic 2.0 License. - The text of the License follows: + The npm application + Copyright (c) npm, Inc. and Contributors + Licensed on the terms of The Artistic License 2.0 + + Node package dependencies of the npm application + Copyright (c) their respective copyright owners + Licensed on their respective license terms + + The npm public registry at https://registry.npmjs.com + and the npm website at https://www.npmjs.com + Operated by npm, Inc. + Use governed by terms published on https://www.npmjs.com + + "Node.js" + Trademark Joyent, Inc., https://joyent.com + Neither npm nor npm, Inc. are affiliated with Joyent, Inc. + + The Node.js application + Project of Node Foundation, https://nodejs.org + + The npm Logo + Copyright (c) Mathias Pettersson and Brian Hammond + + "Gubblebum Blocky" typeface + Copyright (c) Tjarda Koster, https://jelloween.deviantart.com + Used with permission ... - "Node.js" and "node" trademark Joyent, Inc. npm is not officially - part of the Node.js project, and is neither owned by nor - officially affiliated with Joyent, Inc. - - Packages published in the npm registry (other than the Software and - its included dependencies) are not part of npm itself, are the sole - property of their respective maintainers, and are not covered by - this license. + The following additional terms shall apply to use of the npm software, the npm + website, the npm repository and any other services or products offered by npm, + Inc.: + + "Node.js" trademark Joyent, Inc. npm is not officially part of the Node.js + project, and is neither owned by nor affiliated with Joyent, Inc. + + "npm" and "The npm Registry" are owned by npm, Inc. All rights reserved. + + Modules published on the npm registry are not officially endorsed by npm, Inc. + or the Node.js project. + + Data published to the npm registry is not part of npm itself, and is the sole + property of the publisher. While every effort is made to ensure accountability, + there is absolutely no guarantee, warrantee, or assertion expressed or implied + as to the quality, fitness for a specific purpose, or lack of malice in any + given npm package. Packages downloaded through the npm registry are + independently licensed and are not covered by this license. + + Additional policies relating to, and restrictions on use of, npm products and + services are available on the npm website. All such policies and restrictions, + as updated from time to time, are hereby incorporated into this license + agreement. By using npm, you acknowledge your agreement to all such policies + and restrictions. + + If you have a complaint about a package in the public npm registry, and cannot + resolve it with the package owner, please email support@npmjs.com and explain + the situation. See the [npm Dispute Resolution + policy](https://github.com/npm/policies/blob/master/disputes.md) for more + details. - "npm Logo" created by Mathias Pettersson and Brian Hammond, - used with permission. + Any data published to The npm Registry (including user account information) may + be removed or modified at the sole discretion of the npm server administrators. + + "npm Logo" contributed by Mathias Pettersson and Brian Hammond, + use is subject to https://www.npmjs.com/policies/trademark "Gubblebum Blocky" font - Copyright (c) by Tjarda Koster, http://jelloween.deviantart.com + Copyright (c) by Tjarda Koster, https://jelloween.deviantart.com included for use in the npm website and documentation, used with permission. - This program uses several Node.js modules contained in the node_modules/ + This program uses several Node modules contained in the node_modules/ subdirectory, according to the terms of their respective licenses. """ Signed-off-by: Trevor Woerner Signed-off-by: Martin Jansa

nodejs: cleanup and update

2016-01-04T13:56:23+00:00

Remove old nodejs4_0.4.12 and update nodejs_0.12.7 to the latest stable nodejs_4.2.3. Nodejs is picky about which architectures it supports. The supported arch mapping required some updating to bring it up to date with the current nodejs code. Add COMPATIBLE_MACHINE entries so it only builds for the supported architectures. ARM cores that don't support at least VFP2 have been dropped: https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk "Due the increasing cost of the keeping the "no-VFPv2" port of V8 working on ARM, we are planning on making 3.17 the last V8 release that that supports ARM chips without VFPv2. Starting with the 3.18 release, the minimal V8 requirements will increase to ARMv6 + VFPv2. In order to simplify maintenance, we will also remove the "pre-VFP2" ARM code from the V8 code base." Additionally, gcc no longer supports a VFPv2 option: https://gcc.gnu.org/onlinedocs/gcc/ARM-Options.html#index-mfpu-1460 Signed-off-by: Trevor Woerner Signed-off-by: Martin Jansa

nodejs: use oe_runmake to respect PARALLEL_MAKE

2015-11-02T13:59:26+00:00

Signed-off-by: Martin Jansa