On 11/20/2013 2:35 PM, Charles Steinkuehler wrote: >> What do you have in mind for an alternative approach? Looking for local >> >copies of directories/files before hitting the Internet? > I thought about this and chatted with RCN about some options, and the > following approach seems reasonable and shouldn't require too much in > the way of drastic changes. > > There are two parts to what I'm thinking about. One would be a > "preload" command that could be added to the image creation scripts that > would download the current version of the required files so they are in > the MachineKit tarball. This is completely "safe" and can easily be > setup so it won't break RCN's usage of the build scripts.
Thanks, Charles. I remember wondering to myself when I first installed the MachineKit to a microSD card why this wasn't the case already, but I figured there was probably a good reason and let the thought go. At 1700+ lines, RCN's script is wicked long (more than 30 pages if one were so old-fashioned as to print it off). I wasn't going to go poking around it without good reason when all I wanted to do was get a MachineKit-based BBB up and running. Depending on my host and circumstances, it takes me some 20-30 minutes to execute the script (which, incidently, worked just fine several times today). > The other part would be tweaks to the actual setup_sdcard.sh script so > it would use the cached files and not try to pull updates from the > internet. Yep. When I queried you I was thinking that at the very least, the script should, by default, use cached files if present and download and cache them first if not already present. I was thinking they should, by default, be cached somewhere in your directory tree "as if" they were in the tarball. Using /tmp by default is so, well, temporary:-) If RCN is contemplating adding some such capability to his upstream script, then probably an environment variable should be used to override the default directory just as he uses such variables elsewhere. > > RCN already has some switches to do part of this (see --spl and > --bootloader, which affect the LOCAL_SPL, LOCAL_BOOTLOADER and > USE_LOCAL_BOOT variables), but that doesn't support everything currently > fetched online. Also, it would be good if the syntax was simpler to > use. Perhaps something like an --offline switch. I was thinking the default would be to use the cached files while something like an --online switch could override this behavior and force downloading the files so a savvy user could ensure the files being used were up to date. Regards, Kent ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
