Talk:Olpc-update

From OLPC
Revision as of 07:23, 25 December 2007 by Adricnet (talk | contribs) (Simplification needed)
Jump to navigation Jump to search

Feature Requests

A request from a non-programmer for olpc-update and olpc-update-rsync commands:

Provide a --list (-l?) option that shows all available builds (easier to remember)
Provide a --changelog (-c?) option that shows a builds changelog (olpc-update -c build-609)
Provide --help (-h) to explain its usage, and the above options

HoboPrimate 00:04, 5 October 2007 (EDT)

 Done. You'll need very recent pyvserver and rainbow RPMs to try 
 these out. Also, you'll need to convince cscott to put ChangeLogs 
 in the rsync modules. (Or volunteer to do so yourself). 
   -- Michael Stone 01:54, 5 October 2007 (EDT)


When I click latest release, I see no file named osXYZ.usb, I see one called osXYZ.img, osXYZ.toc, etc. but no .usb. What gives?

Simplification needed

Gosh, this page is meaty and full of great stuff. But if we are going to send users to it, it's needs to be way much simpler. Pictures are not out of the question. Alternatively, if there's another page to send users to for this, this we need to link it prominently in eg Support FAQ. (And the Stable_upgrade page is not even as clear as this page is).

On a related note, (why) do you need to specify the branch to get ship.2-653 ? This is counter tho the documentation on this page. Thanks, --Adricnet 02:23, 25 December 2007 (EST)