Robert you have just described how packagekit-offline updates and systemd offline update feature works. 7 lip 2015 02:26 "Robert Xu" <[email protected]> napisał(a):
> On 6 July 2015 at 16:01, Tomasz Paweł Gajc <[email protected]> wrote: > > > > Dnia poniedziałek, 6 lipca 2015 16:35:37 Colin Close pisze: > > > Thanks > > > That clears up the issue a bit for me. Can I get it clear what you are > > > getting at with the "daemonised urpmi" > > > I'm assuming that you are thinking > > > of something like the old dkms init service. > > No! > > urpmi process needs to be detached from current user session, so it can > > survive X11 kill and finish update. > > > > So either daemonise urpmi (split it to client and server), where server > will > > be running rpm install and update as a systemd service, or find a neat > way to > > prevent urpmi process from killing when running in graphical target. > > > > > > You don't need either of those two options. Fedora doesn't even do > those options. I would recommend the following: > > 1. Create a urpmi-distribution-upgrade shell script that looks for the > existence of a new update, adds new sources as necessary, and > pre-downloads all necessary RPMS. > 2. This shell script then creates a new systemd target, > distribution-upgrade.target or something, that calls > urpmi-distribution-upgrade. It then sets systemd to boot to that > target on the next reboot. > 3. The user reboots. The shell script then alerts Plymouth to start > updating a progress screen, and calls urpmi to upgrade with the > downloaded RPMS. It then cleans up the targets and reboots. > > That is essentially how Fedora does it, and we should do the same. > > -- > cheers, Robert :: github.com/robxu9 > _______________________________________________ > OM-Cooker mailing list > [email protected] > http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________ OM-Cooker mailing list [email protected] http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
