Skip to contentSkip to conversation

nodejs: update from 4.2.3 to 4.2.4

PATCH Superseded Trevor Woerner 2 participants 5 messages Dec 30, 2015

v2 of 3 Superseded Latest is v3 →

lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 nodejs: update from 4.2.3 to 4.2.4

Additionally, the LICENSE file changed: Updated node LICENSE file with new npm license:

- npm's license changed from being copyrighted "Isaac Z. Schlueter" to "npm, Inc. and Contributors"; more text was added clarifying the copyrights to things such as the npm logo, the typeface, and trademarks

- further text was added clarifying the separation between npm itself and the various npm packages, their data and licenses

---
 .../recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb}    | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
 rename meta-oe/recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb} (93%)
meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb renamed from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb +3 -3
similarity index 93%
rename from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb
index 66a3c11..18e23b7 100644
@@ -1,7 +1,7 @@
 DESCRIPTION = "nodeJS Evented I/O for V8 JavaScript"
 HOMEPAGE = "http://nodejs.org"
 LICENSE = "MIT & BSD & Artistic-2.0"
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ee90ba97d933fc8d56e97812b7dd62e9"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=963ca39eebcb15ac618bc3006504ae3f"
 
 DEPENDS = "openssl"
 
@@ -12,8 +12,8 @@ COMPATIBLE_MACHINE_mips64 = "(!.*mips64).*"
 SRC_URI = "http://nodejs.org/dist/v${PV}/node-v${PV}.tar.gz \
     file://no-registry.patch \
 "
-SRC_URI[md5sum] = "529a8abd4ca5a2225636767d3f14c382"
-SRC_URI[sha256sum] = "5008ade5feb4b089f59163f66bffddc113f27de5d78edf203e39435c2c5d554f"
+SRC_URI[md5sum] = "86e4d0d8b626f6e60ca7bef02f2543d2"
+SRC_URI[sha256sum] = "4ee244ffede7328d9fa24c3024787e71225b7abaac49fe2b30e68b27460c10ec"
 
 S = "${WORKDIR}/node-v${PV}"
 
Signature · 1 line
2.7.0.rc3
#1 lore raw
Quoted 9 lines · Trevor Woerner

Additionally, the LICENSE file changed: Updated node LICENSE file with new npm license:

- npm's license changed from being copyrighted "Isaac Z. Schlueter" to "npm, Inc. and Contributors"; more text was added clarifying the copyrights to things such as the npm logo, the typeface, and trademarks

Does this mean we need to alter packaging of these files ? are there any commercial implications ?

Quoted 45 lines

- further text was added clarifying the separation between npm itself and the various npm packages, their data and licenses

---
.../recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb} | 6 +++---

1 file changed, 3 insertions(+), 3 deletions(-)

rename meta-oe/recipes-devtools/nodejs/{nodejs_4.2.3.bb => nodejs_4.2.4.bb} (93%)

meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb renamed from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb +0 -0
similarity index 93%
rename from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb
rename to meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb
index 66a3c11..18e23b7 100644
@@ -1,7 +1,7 @@

DESCRIPTION = "nodeJS Evented I/O for V8 JavaScript" HOMEPAGE = "http://nodejs.org"
LICENSE = "MIT & BSD & Artistic-2.0"

meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb renamed from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb +1 -1
-LIC_FILES_CHKSUM = "file://LICENSE;md5=ee90ba97d933fc8d56e97812b7dd62e9"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=963ca39eebcb15ac618bc3006504ae3f"

DEPENDS = "openssl"

meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb renamed from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb +0 -0
@@ -12,8 +12,8 @@ COMPATIBLE_MACHINE_mips64 = "(!.*mips64).*"
 SRC_URI = "http://nodejs.org/dist/v${PV}/node-v${PV}.tar.gz \
    file://no-registry.patch \

"

meta-oe/recipes-devtools/nodejs/nodejs_4.2.4.bb renamed from meta-oe/recipes-devtools/nodejs/nodejs_4.2.3.bb +2 -2
-SRC_URI[md5sum] = "529a8abd4ca5a2225636767d3f14c382"
-SRC_URI[sha256sum] = "5008ade5feb4b089f59163f66bffddc113f27de5d78edf203e39435c2c5d554f"
+SRC_URI[md5sum] = "86e4d0d8b626f6e60ca7bef02f2543d2"
+SRC_URI[sha256sum] = "4ee244ffede7328d9fa24c3024787e71225b7abaac49fe2b30e68b27460c10ec"

S = "${WORKDIR}/node-v${PV}"

--
2.7.0.rc3

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#2 lore raw
Quoted 10 lines · Khem Raj
Quoted 8 lines · Trevor Woerner

Additionally, the LICENSE file changed: Updated node LICENSE file with new npm license:

- npm's license changed from being copyrighted "Isaac Z. Schlueter" to "npm, Inc. and Contributors"; more text was added clarifying the copyrights to things such as the npm logo, the typeface, and trademarks

Does this mean we need to alter packaging of these files ? are there any commercial implications ?

I'm not a lawyer so I can't say for certain and, to be honest, I don't spend much time understanding all the licensing issues revolving around Free/OpenSource Software, but both before and after this change the licensing of npm itself was and is Artistic License 2.0.

before:

-    Copyright (c) Isaac Z. Schlueter
-    All rights reserved.
-    npm is released under the Artistic 2.0 License.
-    The text of the License follows:

after:

+    The npm application
+    Copyright (c) npm, Inc. and Contributors
+    Licensed on the terms of The Artistic License 2.0

... and then it goes on to mention that npm packages are licensed by their creators, npm isn't responsible for them or their contents, and specifies the ownership of various trademarks, logos, and the licensing of the typeface used on their website.

So my best guess is that nothing has changed other than a legal entity was created "npm, Inc." to oversee npm instead of one person being personally responsible. But, like I said, I'm no expert in these things.

#3 lore raw
Quoted 12 lines · Trevor Woerner
Quoted 8 lines · Khem Raj
Quoted 8 lines · Trevor Woerner

Additionally, the LICENSE file changed: Updated node LICENSE file with new npm license:

- npm's license changed from being copyrighted "Isaac Z. Schlueter" to "npm, Inc. and Contributors"; more text was added clarifying the copyrights to things such as the npm logo, the typeface, and trademarks

Quoted 7 lines
Quoted 2 lines

Does this mean we need to alter packaging of these files ? are there any commercial implications ?

I'm not a lawyer so I can't say for certain and, to be honest, I don't spend much time understanding all the licensing issues revolving around Free/OpenSource Software, but both before and after this change the licensing of npm itself was and is Artistic License 2.0.

Yes. please include exact diff instead of summarizing as your patch does.

Quoted 26 lines

before:

(quoted diff) +0 -4
-    Copyright (c) Isaac Z. Schlueter
-    All rights reserved.
-    npm is released under the Artistic 2.0 License.
-    The text of the License follows:

after:

(quoted diff) +3 -0
+    The npm application
+    Copyright (c) npm, Inc. and Contributors
+    Licensed on the terms of The Artistic License 2.0

... and then it goes on to mention that npm packages are licensed by their creators, npm isn't responsible for them or their contents, and specifies the ownership of various trademarks, logos, and the licensing of the typeface used on their website.

So my best guess is that nothing has changed other than a legal entity was created "npm, Inc." to oversee npm instead of one person being personally responsible. But, like I said, I'm no expert in these things. --
_______________________________________________
Openembedded-devel mailing list [email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#4 lore raw
Quoted 1 line · Khem Raj

Yes. please include exact diff instead of summarizing as your patch does.

LICENSE +0 -0
index 7920cbb..ea51cc4 100644
@@ -338,11 +338,32 @@ The externally maintained libraries used by

Node.js are:
- npm is a package manager program located at deps/npm. npm's license follows:
"""

-    Copyright (c) Isaac Z. Schlueter
-    All rights reserved.
+    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.
-    npm is released under the Artistic 2.0 License.
-    The text of the License follows:
+    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
     --------
@@ -554,24 +575,49 @@ The externally maintained libraries used by
Node.js are:
     --------
-    "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.
+    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.:

-    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.
+    "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 Logo" created by Mathias Pettersson and Brian Hammond,
-    used with permission.
+    "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 [email protected]
and explain
+ the situation. See the [npm Dispute Resolution
+ policy](https://github.com/npm/policies/blob/master/disputes.md)
for more
+ details.
+
+ 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.
"""