On 10/05/2016 03:00 AM, Adam Williamson wrote:
On Tue, 2016-10-04 at 20:43 -0400, Sam Varshavchik wrote:
But ordinary regular app updates will happily run on cruise control, without
bringing the system down into single user mode. If Android can do that, I
see no reason why Fedora can't, either. The only time you need to reboot an
Android device is for a kernel-level update.
No, in fact, it's for any *system level* update. Any change to the
underlying system (as opposed to an app) requires the full reboot
treatment. Only updates to app packages don't.
Even that depends on what the “app” is doing. If the format of data
files changes in an incompatible way (or just their location on the file
system
The reason Android can do fairly good app updates is precisely because
it does exactly what Flatpak and Snappy are trying to do for Linux:
hard separation between app space and system space.
I seriously doubt that is the reason.
This looks much more relevant:
<https://developer.android.com/guide/components/activities.html#ImplementingLifecycleCallbacks>
Basically, the system can kill applications which do not run in the
foreground at *any* time to recover resources. This facility can also
be used to transparently update system components on which applications
depend.
> We can't realistically do it with the 'distribution is just a big pile
> of RPMs' model.
The lack of application state management which mirrors what mobile
platforms are doing is hardly an RPM issue.
Florian
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
