Developing and Deploying devices

[Jeroen Massar]

On 2016-04-14 16:55, Dirk Hohndel wrote:
> 
>> On Apr 14, 2016, at 7:50 AM, Jeroen Massar <jeroen at massar.ch> wrote:
[..]
>> Thus, if we go the image route, and the KISS-setup that we are going for
>> will likely imply that, then we just use this recovery feature to flash
>> a new version onto the device.
> 
> Have you looked at the cool thing CHIP just announced?
> With a chrome browser go to flash.getchip.com  - you can reflash your
> CHIP from a web browser... which means that all we need to work on
> with NextThing is how to get our image into their collection of images
> and then our users can simply flash it from their browser - no advanced
> knowledge required.
> 
> I really like the idea that we don't need to re-invent any of that infrastructure
> and can simply re-use what NextThing is working on already - which to me
> makes this so attractive to use the CHIP

Wow, basically the CRX contains the flasher app (mac executeable in OSX
case), thus this is platform specific contains all the right bits to
access USB, and that is it, that you just download through Chrome.

Flashing does take ~12 mins apparently, dropping to 9 mins, and then
getting stuck... mmmm

If they have a 'store' of apps there, (like the headless version) then
we are done, that is EXACTLY what we need. We then just need the ability
to give them updates (hopefully PGP signed!) images once in a while.
(read: when libdivecomputer gets support for a new DC or a major fix etc).


>From a developer perspective though, it will still mean Debian packages
that we install on top of the latest image of their default image.
(unless people want to live with 'make install', which works, but is
icky imho ;)

Greets,
 Jeroen