On Tue, 2011-06-14 at 10:21 +0800, Xiangfu Liu wrote:
> > * Finish the web update: make it more robust (for example it freezes
> > when run without an internet connection), use releases, check versions,
>
> one small question. what is the 'Check versions' for in software update
> dialog?
Count the number of patches in /ssd/patchpool, update the "Installed"
column for that one, then fetch SoC/BIOS and Flickernoise versions and
the number of patches on the remote server, and update the "Available"
column.
> it's for check if the server have a new version, then update the 'Available'
> then let people decide whether he want update? if that button is for that
> I think we can just merge that two buttons to one.
The "Check versions" button only updates the display, but not flash
anything.
The "Update from web" button:
1) updates the display (same as "check versions" button)
2) proceeds to download and flash SoC, BIOS and Flickernoise if either
a) installed and available versions are different - OR -
b) system is in rescue mode (so people can simply reinstall the
main software from rescue mode with one click)
3) downloads and stores all patches which are present on the server but
not in /ssd/patchpool. Simply match them by filename. Do not delete
local patches which are not present on the server, as the user might
have modified them. We can come up with a more sophisticated update
system later, I think this one should be enough for now.
I don't think the two buttons should be merged into one (but the "check
version" code should).
> > implement a basic patch pool (simply download the new patches which are
>
> where should the patchpool update button be? included in 'web update'?
Yes.
S.
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkymist@Freenode
Twitter: www.twitter.com/milkymistvj
Ideas? http://milkymist.uservoice.com
