By the way, the package I built from source, would work on any armhf, using the same libc. Which I forget which version comes on the latest beaglebone images. but a good guide is that whichever system you want install it on uses the same version of gcc. So in this case, the package I built for my beaglebones was built on a Raspberry Pi 3 running Raspbian Jessie, with gcc 4.9.x.
The point I'm trying to make here, is that this package would, and does work for more than just the beaglebones. On Sun, Dec 18, 2016 at 12:15 PM, William Hermans <[email protected]> wrote: > > > On Sun, Dec 18, 2016 at 11:56 AM, Stephane Charette < > [email protected]> wrote: > >> By default when I install a BB with one of the usual RCN builds, the >> repos as defined in /etc/apt/sources.list are set to the following: >> >> deb http://httpredir.debian.org/debian/ jessie main contrib non-free >> deb http://httpredir.debian.org/debian/ jessie-updates main contrib >> non-free >> deb http://security.debian.org/ jessie/updates main contrib non-free >> deb https://deb.nodesource.com/node_0.12 jessie main >> deb [arch=armhf] http://repos.rcn-ee.com/debian/ jessie main >> >> Are there other well-known ARMHF repos that I can add if the package I'm >> looking for isn't there? >> > > Well this is a problem. "well known" does not necessarily imply "secure". > All those listed above except for the nodesource, and RCN repo's are > official. Personally, I would not add the nodesource repo, but have no > qualms with Roberts repo. > >> >> For example, I like to use "fish" as my shell. When I try to install it, >> I get this: >> >> $ *sudo apt-get install fish* >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Package fish is not available, but is referred to by another package. >> This may mean that the package is missing, has been obsoleted, or >> is only available from another source >> E: Package 'fish' has no installation candidate >> >> Yes, I could build it myself, but that defeats the entire purpose of >> having package management, automatic updates when security fixes are >> available, etc. >> > > So build the package once, and use it multiple times. This is one reason > why I would not use the nodesource repo. I build my own Nodejs, from source > tarballs my self. Currently I have a Nodejs 4.6.2 *deb, that I install on > any system that needs it. Just a simple file transfer, and sudo dpkg -i > <package name> away. > > -- 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/CALHSORqrfWZTj3pXjvhJA1%3D9um1fsPU_%3DCChitWaxtU9e7HtHg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
