On Mon, Feb 18, 2013 at 8:18 PM, Cristian Rodríguez
That's exactly how systemd does it. =)
Maybe I am misunderstanding something.
SUSE's package manager zypp install packages one by one,this is done by executing the rpm binary. there are no transactions involved and there is no warranty of consistency either.
Yes.This is madness, but it is the way it works.
systemd of course does not have a package manager, so it must call zypper up or dup with the appropiate parameters in order to behave exactly like a human-made upgrade.
Does the implementation internally do this or is calling rpm directly ?
Oh... I think I can now understand what happens with gnome's updater that I attributed to running rpm package by package. I've never actually experienced interrupted installations (only interrupted downloads - and zypper handles them pretty well). Gnome's dependency resolution must be broken somehow, because the kinds of breakages I experienced usually related to dependencies and wrongly mixing repos (in a way zypper never mixed). Note: this applies to apper/packagekit too. I've stopped using all desktop-provided updaters because of this. Anyway, transactions are a good thing, and what systemd does is actually quite beneficial even if done without FS snapshots (because far fewer failure modes are possible when committing the transaction than they are during preparation of it). The rebooting thing is the only problem here. Zypper does have the information of whether or not a reboot is required for updates, so the system needs only inform systemd and gnome about it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org