On 04/24/2013 02:30 AM, Josef Reidinger wrote:
But I see one quite big disadvantage of D-Bus. It is different API that is not so easy for users to try it. If something goes wrong, we see in log that systemctl command fail and user can try to run it manually.
systemd logs its actions and the result of dbus methods calls etc. it is just a matter of increasing the verbosity level. If this is a problem, It can be solved by logging the calls from yast in an structured fashion to the journal. (there is also a rubygem to access and use the journal, but no idea of its state) Using CLI is also for me more unix way,
where is CLI and gui is build on top of it, so result is that CLI is central point which is well tested and GUI benefit from it.
well, fact is systemd is designed this way: - humans interact with it using command line tools,the output changes all the time,return values of these tools are not part of any stability promise. (only the execution "verbs" of systemctl are) - programs interact via d-bus or the C API (the latter is probably not of much use for yast except the logging part) It is "everything is an api" not "everything is command" ;) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org