On Sat, 2008-10-04 at 11:34 -0400, Colin Walters wrote: > 2008/10/4 Tim Lauridsen <tim.lauridsen@xxxxxxxxxxxxxx>: > > > > Hmmm. > > 1. yum-cli -> yum-api -> pk-con -> pk -> DBUS -> pk-backend -> yum-backend > > -> yum-api -> install the package > > > > compare to > > > > 2. yum-cli -> yum-api -> install the package > > You could also use the python dbus bindings directly, or python > bindings for libpk. > > > here is kind og chicken and egg problem here. > > There's no chicken-egg - the patch would look like this: > > if 'DBUS_SESSION_BUS_ADDRESS' in os.environ: > if cmd == 'install': > execv(['pkcon', 'install', sys.argv[1:]]) > elif cmd == 'search': > execv(['pkcon', 'search', 'name', sys.argv[1:]) > # ..and maybe a total of 3-4 more commands. Personally, I only use those two. > > > take this user case. > > > > ssh to some server > > yum install foo > > how would that work. > > With a change like the above, it would be unaffected, at least for now. > > > Dont forget that PackageKit is a highlevel abstraction to the low level > > package management system, making the low level system use the highlevel > > abstraction of it self, is kind of crazy. IMHO. > > The (first) lower level system is yum-api, yum-cli and pkcon are > really at the same level. It would make sense long term to having them > be more merged. They're not at the same level. yum-cli talks directly to the api. pkcon talks to the pk dbus interface which then talks to the yum-module for pk which then talks to the yum api. -sv -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
