On Wed, Nov 16, 2016 at 1:56 PM, William Hermans <[email protected]> wrote: > On Wed, Nov 16, 2016 at 8:28 AM, Robert Nelson <[email protected]> > wrote: >> >> On Wed, Nov 16, 2016 at 6:00 AM, William Hermans <[email protected]> >> wrote: >> > I think it may be wise to at least provide build instructions for 4.x. >> > In >> > case something someone needs in addition to the packages you provide >> > are reasonably guaranteed to be usable. If not by one version but by >> > another. >> >> We stopped building nodejs, we use the repo provided by nodesource: >> >> https://github.com/nodesource/distributions > > > And this is why I refuse to use the version of Nodejs, or whatever it is > that's provided by your APT repo. >> >> >> >> Our jessie images have had this enabled for most of the last year: >> >> deb https://deb.nodesource.com/node_0.12 jessie main >> #deb-src https://deb.nodesource.com/node_0.12 jessie main >> >> and upgrade to v6.x is just to change that too: >> >> deb https://deb.nodesource.com/node_6.x jessie main >> #deb-src https://deb.nodesource.com/node_6.x jessie main >> >> > Anyway I can provide build instructions for 4.2.6( from source ). It's >> > actually very easy. But as for NodeRED, and the rest . . . I have no >> > hands >> > on. I do actually prefer using NPM to install the few packages I use. >> > Despite disliking NPM with a passion. I try to limit my NPM package >> > installs >> > to Path, socket.io, and Express when at all possible. >> >> node-red takes about an hour on the bbb, it also needs 512MB of swap >> enabled, you can take a look at my script i use to pre-build the >> project into our deb package: >> >> https://github.com/rcn-ee/npm-package-node-red >> > You misunderstand me. I have absolutely no interest in NodeRED, or any of > that other "hooey". But I figured that support for your other Node packages > might be important to you. > > When it comes to Node, or honestly most anything, I'm a purist. I like to > keep things a stock as possible. This way, there are very few surprises, and > if there are. Well then all I have to do is read the official documentation. > So when I hear that you're "not using Nodejs any more, but using nodesource. > .." I tend to view that as polluting the Linux image we're using. Because > quite honestly I have no idea wtf this source really *is*
Sorry, you must have miss-understood my message.. We stopped building/packaging nodejs on "my" own, instead we use the version of nodejs from the nodesource repo.. They build it directly from nodejs proper.. As they provide, repos for these versions v0.12.x v4.x v6.x Including the odd ducks: v0.10.x iojs_1.x iojs_2.x iojs_3.x v5.x v7.x Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYhoQs7cQOFLDxJXNGFefBh90a_7-pK%3DKXGJnGGN7_EkmQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
