PNG  IHDR;IDATxܻn0K )(pA 7LeG{ §㻢|ذaÆ 6lذaÆ 6lذaÆ 6lom$^yذag5bÆ 6lذaÆ 6lذa{ 6lذaÆ `}HFkm,mӪôô! x|'ܢ˟;E:9&ᶒ}{v]n&6 h_tڠ͵-ҫZ;Z$.Pkž)!o>}leQfJTu іچ\X=8Rن4`Vwl>nG^is"ms$ui?wbs[m6K4O.4%/bC%t Mז -lG6mrz2s%9s@-k9=)kB5\+͂Zsٲ Rn~GRC wIcIn7jJhۛNCS|j08yiHKֶۛkɈ+;SzL/F*\Ԕ#"5m2[S=gnaPeғL lذaÆ 6l^ḵaÆ 6lذaÆ 6lذa; _ذaÆ 6lذaÆ 6lذaÆ RIENDB` You'll need a fairly up to date system -- some of the build files are generated, and the input used to generate them may be specific to whichever version of the autotools I had installed on my box when I committed the input files to git. If everything's set up correctly, this is all you need to do: ./autogen make all dist rpmbuild -tb oddjob-*.tar.gz If you're looking to add a new service/object/interface/method to the list of those which can be invoked, create a new D-Bus config file under /etc/dbus-1/system.d which allows users to issue requests to your oddjobd-backed service (you'll need to restart D-Bus so that it will read this file), and create an oddjobd configuration file under /etc/oddjobd.conf.d to get oddjobd to accept those requests and to know what to do with them (you'll need to restart or SIGHUP oddjobd so that it will read the file).