Is that "avoid activating a new system package and *avoid requiring* the user to reboot" or "'avoid activating a new system package' AND 'require the user to reboot'"? On Wed, Apr 23, 2014 at 1:27 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > On 23.04.2014 09:34, Stephan Aßmus wrote: > >> There is work going on to make the whole concept of installing a newer >> nightly on top of an existing installation obsolete. The system should >> just update itself, which was one of the reasons for having package >> management in the first place. From reading the recent commits in this >> regard, I take it this update feature is not yet complete. >> > > In theory, given a newer repository, at least pkgman can already update > the system to a newer version. In practice the process still has a few > issues, since all the system packages are replaced live, which can (and > usually does) lead to hiccups (like system crashes). My intended solution > for this issue is to avoid activating a new system package and require the > user to reboot. > > This leads to a situation where the set of installed packages differs from > the set of active packages, which is a something the package daemon and the > package managers (pkgman, HaikuDepot) need to be able to deal with. A > similar situation occurs when booting into an old state (*) and is easier > to reproduce, so I decided to implement that first. > > I'm currently working on that very topic, but due to my limited Haiku time > progress is relatively slow. > > CU, Ingo > > (*) When installing/uninstalling/updating packages via pkgman or > HaikuDepot the package daemon backs up the previous state of the installed > packages. Since sometime last week the boot loader allows selecting such an > old state to boot into. So, if an update breaks something (even the boot > process) unexpectedly, it is possible to boot into the working old state. > > >