Am 12.04.2016 um 16:36 schrieb Dirk Hohndel: > >> On Apr 12, 2016, at 4:53 AM, Martin Gysel <m...@bearsh.org> wrote: >>> The other thing is deployment. Initially, that’s simple, we provide disk >>> images. But then, what is the upgrade path? Connect to wifi and do git >>> pull? apt-get upgrade/update? Get a new disk image? That needs to be >>> thought about as well for devices like this. >> >> I think it depends on the used base. if it's a debian based system (and >> I would start with such a system), then providing a apt-get urls seems >> to be the easiest solution. if using a leaner base (e.g. to reduce >> startup time as much as possible) then flashing a whole image and/or >> replace changed files (using a script or so) may be the best way. > > Martin, I love your optimism. And I can tell that you are not part of the > people > here who try to support our end users. I recommend that you go through our > user forum and our FB page and look at the questions we are getting. > > No, this cannot be based on apt-get URLs.
maybe you misunderstood me, I'm not proposing to have the enduser type apt-get ..., rather let the system update itself using apt-get. but event then, you might be right, it can cause troubles to the enduser when e.g. there's a power failure in a critical phase of the upgrade. /martin _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
