On Thu, 2005-03-03 at 09:23 -0500, seth vidal wrote:
>> I think that's the first step. I'll try and play today.
>>
>
>here's the simplest form of the class to do the checking.
>
>it doesn't do anything other than setup, build the updates/obsoletes and
>iterates them.
>
>I don't have any dbus knowledge, yet, so I don't have the event sending
>in there, of course.
Noddy dbus example.
Drop yum.conf in /etc/dbus-1/system.d
/sbin/service messagebus restart
in a terminal on the console run
dbus-monitor --system
elsewhere sudo python yum-test-check.py
See the lovely output:
string:('evolution-webcal', 'i386', '0', '2.1.92', '1')
signal interface=edu.duke.linux.Yum; member=updates; sender=:1.10
string:('up2date-gnome', 'i386', '0', '4.4.9', '1')
signal interface=edu.duke.linux.Yum; member=updates; sender=:1.10
string:('cups', 'i386', '1', '1.1.23', '12')
Paul
Attachment:
yum-test-check.py
Description: application/python
<!DOCTYPE busconfig PUBLIC "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd";> <busconfig> <policy user="root"> <allow own="edu.duke.linux.Yum"/> <allow send_destination="edu.duke.linux.Yum"/> <allow send_interface="edu.duke.linux.Yum"/> </policy> <policy at_console="true"> <allow receive_sender="edu.duke.linux.Yum"/> <allow receive_interface = "edu.duke.linux.Yum"/> </policy> <policy context="default"> <deny own="edu.duke.linux.Yum"/> <deny send_destination="edu.duke.linux.Yum"/> <deny send_interface="edu.duke.linux.Yum"/> </policy> </busconfig>
-- Fedora-config-list mailing list Fedora-config-list@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-config-list