Hi Marguerite,
On Sat, 20 Sep 2014 20:42:11 +0800
"marguerite"
Hi, Joachim,
Can we submit npm w/ all its dependencies and related tools like gyp to Factory before Beta?
Yes, of course. I actually wanted to do that on Friday but had to leave the office on short notice.
npm is now a separate package, thus the nodejs in Factory is now not able to build anything nodejs. But there're packages in Factory seem to rely on npm to build.
I split it off because I figured just for running the prepackaged node.js packages, npm is not required so why force installing it.
So we now face a mut-be-done choice:
1. fix the packages in Factory by the "manual copy" method to avoid using of npm 2. drop the packages (and even nodejs itself) from Factory, guide our users to use d:l:nodejs to develop their nodejs applications. 3. submit the splitted stuff to Factory, which will be ?50 packages, before Beta.
I think we'll want to have node.js support in Factory eventually, so we might as well go ahead and submit them.
BTW, I don't like the "manual copy" method, which is:
1. changeable over releases (if upstream add new files, your package will success anyway) 2. too much things needed to be judged by human-being (like which one to copy?) 3. it may needs a local test environment for the packager, which will force the packager to be a real nodejs developer. So it'll break our BURP way of packaging.
and actually this method can be done by robots like things done by our perl CPAN robots. It undervalues human-being, or even challenges human-being because we are much more easy to get things wrong than a robot.
I agree in theory that having a generic installation method is preferable to doing it manually, however the npm local install command has its downside too IMHO. npm install simply copies the whole package into the node_modules directory, including documentation, test files, potentially included packages the package depends on, even dotfiles like .gitignore. This means you have to manually clean up after npm anyway, which kinda defeats the point of using it.
But anyway this way is super fast, we can package 50 packages for one night. Anyway if we want to keep both ways of packaging ("manual copy" && "patch package.json") available, we still need to make a decision whether or not to submit those development tools to Factory.
Given that npm was in Factory before we actually removed functionality, so I think it should go back in asap. I'll submit it. Btw, thanks for fixing all the spec files. Cheers Joe -- ISV Technical Manager SUSE LINUX Products GmbH -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org