> > I'm going to pre-build the package on jessie with nodejs v0.12.x and ship > it to the jessie users as is. ;) (well the deb package has a hard > requirement of nodejs (>= 0.12.13))
Yeah . . . I'm using node -v: *v4.2.6* npm -v: *3.9.0* Part of my own problem is that I am following a few different guides on technologies I do not know all that well. So I'm forced to use the packages these people are using until I understand things better. The problem being, many of these guides in using, the packages they mention require current versions of node. I tried using v0.12 / v0.10 version of node, and for the purpose of the guides I'm following - They failed( broken dependencies ). I'm also still learning how things work package wise as for what exactly is really needed when you finish a project. It's currently what I'm calling "dependency hell". As in there is so much bloat / garbage, it's hard to figure out what truly is needed in order for the application to work properly. On Thu, May 26, 2016 at 12:37 PM, Robert Nelson <[email protected]> wrote: > > > On Thu, May 26, 2016 at 2:26 PM, William Hermans <[email protected]> > wrote: > >> it's an extra step before updating the *.deb package, requires a >>> dedicated bbg for pre-building the *.tar.xz, but my sanity has never been >>> better! ;) >> >> >> So, I can tell you have not recently done anything like sudo npm install >> -g phantomjs . . . where phantomjs only has x86 / x86-64( maybe amd64 ) >> binaries. I have, and then spent 3 days trial and error compiling phantomjs >> on my rpi3 ( more memory, and more cores . . .), when i finally got it >> compiled, and installed locally. . . the flipping package that needed >> phantomjs *still* barfed on installation . . . as the other crap needed arm >> binaries too, and no way in hell I was going ot step into that huge pit. >> > > Yeah, that still happens for me too.. > > >> >> It turns out that I only needed that package anyhow for a development >> dependency for some stupid other package that I do not need when deployed. >> . . . So I can write the code on an x86 machine, and just rip the needed >> source out for deployment onto the BBB . . . >> >> So your sanity is different form mine in that you seem to have learned >> to just bypass the whole npm situation, where as a Nodejs developer - I >> can't. Trust me though, I really wish I could, and it is partly why I'm >> writing my own Javascript wrapper for the BBB's sysfs access to the >> peripherals. >> > > > Yeah, my sanity is a little different.. > > Initially i was trying to have the deb package run "npm -g install xyz" > and update it on the user platform based on the version of nodejs.. > > I've changed that too: > > I'm going to pre-build the package on jessie with nodejs v0.12.x and ship > it to the jessie users as is. ;) (well the deb package has a hard > requirement of nodejs (>= 0.12.13)) > > 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/CAOCHtYh_o_kzpoNjh9mLfoMns9eY9yWwfS99Rq9gGcp_C-ix7g%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CAOCHtYh_o_kzpoNjh9mLfoMns9eY9yWwfS99Rq9gGcp_C-ix7g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CALHSORq4JmppqpL1AEfPqB5pzkGT-RRPo1YsYRKAZYO_HFD6MA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
