Stoker wrote: > > JackofAll: When I do the update is the OS F19 R7 the best version to > base the updated guide on. Also, not totally sure how to handle the > instructions for downloading the image files now that the original > method has been disabled. >
Ian, how are you? Hope you are well. I'd suggest not putting much/any effort into updating the guide until the F20 image is released. There are several reasons for this...... To cut a long story short.... (And I hope this doesn't come back to bite me in the arse net week with a bunch of "are we nearly there yet". ) I'm waiting, and have been waiting for some time for a BeagleBone Black to be delivered. Looking at the current tracking info, I'm hopeful to have it on Tuesday. What is going to happen, is as soon as I have been able to test the F20 image on the BBB, is you are going to see the release of three F20 images. One for the WB, another for the Cubietruck and the BBB image. The "new" guide will need to take that into account. At the moment, having not released any F20 image, I'm at liberty to do whatever I like with the F20 arm repo, without worring about the upgrade path on any F20 package already released on an image. The only way this is supportable for me, is by having one base image (and repo), trying to get as much of the "shared" as possible into the base arm repo, and then having board specific repos that depend on the base repo for as much as they possibly can, to avoid duplication. So, we have a base repo, 'F20 armhfp' (http://www.communitysqueeze.org/repo/20/armhfp). The BeagleBone specific repo, 'F20 BeagleBone armhfp' (http://www.communitysqueeze.org/repo/20/beaglebone/armhfp). The Cubietruck specific repo, 'F20 CubieTruck armhfp' (http://www.communitysqueeze.org/repo/20/cubietruck/armhfp). The Wandboard repo, 'F20 WandBoard armhfp' (http://www.communitysqueeze.org/repo/20/wandboard/armhfp). I have been, even as recently as yesterday making changes to packages in the base repo, (in this case, to put both the WB and CT bluetooth firmware loaders into a shared package), changing dependencies as a result. It would have been a nightmare for me, if I'd had to care about update/upgrade paths for existing users. But having not released a F20 image, the only person I "break" is myself. But with the latest raft of changes I'm pretty confident, that as soon as I have the BBB in my hands, and am able to sign-off on "it boots for me", I don't have any more substantial changes to make. Et voila, the F20 images magically appear. Anyway, I'm off at a tangent. As I see it, don't worry about the guide right now, but if you could update it after the release of the F20 images, that would be much appreciated. ------------------------------------------------------------------------ JackOfAll's Profile: http://forums.slimdevices.com/member.php?userid=3069 View this thread: http://forums.slimdevices.com/showthread.php?t=99395 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
