-1 to urpmi as a daemon. It's not built to act as a daemon. And additionally what if an update breaks the system (which it shouldn't, but who knows, someone might not want to update their system)? I would rather not have it as a service that runs on a timer. We're not Windows.
However, +1 to using systemd to run urpmi on distribution upgrades, or reboot and upgrade. I can get behind that. That's what Fedora does, and I fully support it. On 20 April 2015 at 05:02, Tomasz Gajc <[email protected]> wrote: > Hi, > > these days with all that fancy systemd stuff like services or timer, it is > easy to automate some processes. > > I was thinking about running urpmi as systemd service triggered by a timer > (X times per day/week/month). > > What are benefits or having urpmi as a daemon ? > > 1. Smooth upgrade > > As urpmi is running by mdkonline, rpmdrake or in graphical console, some > gig updates may break current session and user will end in broken system. > > 2. Ease upgrade > > I think this will help with KDE4 -> Plasma5 update, as when installing > new desktop environment may cause X11 session to die, for certain when > switching to from X11 to Wayland. > > > What urpmi is missing ? > > Urpmi does not use D-BUS or any IPC (mdkonline is not that kind) that will > help users to interact with urpmi running as a systemd service. > > > There is even more safe way to perform updates with using > http://www.freedesktop.org/wiki/Software/systemd/SystemUpdates/ but > currently this does not work, and i'm trying to figure it out what is > missing here. > > WDYT ? > > > _______________________________________________ > OM-Cooker mailing list > [email protected] > http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org > -- cheers, Robert :: github.com/robxu9
_______________________________________________ OM-Cooker mailing list [email protected] http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
