I have an existing package that has a new version with a dependency on
lodash-node so I was trying to package it but ran into the question of
exactly what it is and how to deal with it...
We have lodash packaged already and as bast I can figure out lodash-node
is the result of using lodash-cli to build node modules from lodash.
Though I'm not sure what that means when lodash is already a node module?!?
In any case does that mean I should package lodash-cli first and then
make the lodash-node package do that build step?
Tom Hughes (tom(a)compton.nu)
Hi T.C. (and cc to nodejs(a)l.fp.o for interest),
I've come up with a solution that I didn't notice before that will allow
us to package jQuery for f20/f19/el6. We still can't currently package
js-zlib for those branches, but we can work around it by cutting the
dependency tree a little short.
The heavily abbreviated dependency tree looks something like this:
js-zlib (cannot be packaged for f20/f19/el6)
grunt-contrib-uglify only uses maxmin for displaying the size of a file,
the minified size, and the gzipped size. It's not such a big loss if we
don't display the gzipped size, which is a tiny feature of
grunt-contrib-uglify. This output is just informational after running
"grunt uglify" to minify your project.
So, if I patch out the use of gzip-size in maxmin, then problem solved.
EL6 update (part of massive update):
Also, EL6 is broken without the massive update I linked above. Can some
kind souls give a couple karma points please? That would be awesome.
On Mon, Mar 31, 2014 at 10:44 AM, Jamie Nguyen <j(a)jamielinux.com> wrote:
> Alternative suggestion:
> %nodejs_fixdep --caret async
> %nodejs_fixdep --caret
Sorry for the delay here; everything discussed in this thread has now
been implemented (incorporating Jamie's suggestions) and filed as a
buildroot override for all active releases.
Also, I added nan to the list of multiply versioned modules so you can
go forward with that. (Please rebuild both versions or future
packages that depend on the newer versions with look in the new
location instead of the old location!)