The the Node.js guidelines say about Source0 :
"The canonical method for shipping most node modules is tarballs from
the npm registry"
"This method [PP: tarbals from npm] should be preferred to using
checkouts from git or automatically generated tarballs from GitHub."
But I think that in following cases it would be better to use sources
from the upstream project:
1) When the license is not included in NPM but is in upstream project.
o Because we are not supposed to ship the license separate from the
2) When the tests are not included.
o In this case we need to download the sources from NPM and from
upstream project, which seems redundant and a waste of work.
3) When NPM content is generated and source files are not in NPM.
o This would mean to download sources from NPM and upstream project,
delete the NPM sources in prep and generate the files again.
Are there good reason to enforce the use of NPM sources which I am
missing? What is your opinion?
I would like to suggest to ad those three exceptions to the guidelines.
I'm still working on packaging up the dependencies for nodejs-ava and a
newer version of nodejs-tap -- but I've run into the problem that we have a
lot of packages that depend on version 4.x of nodejs-chalk, and some of
the new dependencies I'm packaging up depend on chalk >= 1.
I'm proposing creating a new nodejs-chalk0 package that continues with the
0.4.0 branch for now, and that we move the existing nodejs-chalk package to
I'll have a new nodejs-chalk0 package up for review shortly, and I already
have a locally installed copy of nodejs-chalk 1.1.1 so that piece is mostly
taken care of.
The one thing I'm unsure about is the lua pre-transaction scriptlet. Can
someone please explain why they're needed, and whether I need them on both
nodejs-chalk0 and nodejs-chalk, or just one or the other?
Also, who has permissions to the nodejs-packaging repo to be able to add
chalk to the "multiver_modules" list?
You may have noticed that there are quite a few builds being reported as
failing in koschei with SEGV errors during testing.
The bad news is that it seems that the builds of node done with gcc 6
seem to have some sort of problem that results in random crashes during
garbage collection runs.
I can reproduce it in a rawhide VM that predates the rebuild just by
updating the nodejs package to the nodejs-4.2.4-5.fc24 build from the
mass rebuild. Going back to -4 fixes it.
I have tried updating node to 4.2.6 but that hasn't helped.
The crash, according to gdb, normally seems to be somewhere in v8 during
a garbage collection run.
Tom Hughes (tom(a)compton.nu)