Docu updates per event handling

2 files changed, 5 insertions, 19 deletions

diff --git a/doc/EVENTS b/doc/EVENTS
index 9b036fe2c..0e7127f9a 100644
--- a/doc/EVENTS
+++ b/doc/EVENTS
@@ -2,16 +2,18 @@
 handling core.  The following are the events which get fired at
 appropriate points during the build process:
 
+TaskStarted:
 TaskFailed:
 TaskSucceeded:
 
 	The task status event classes have a 'task' attribute, which is
-simply a string containing the task which succeeded or failed.  They also
+simply a string containing the task to which this event applies.  They also
 have a 'data' attribute, which contains the environment data of the package
 in question.
 
-PackageSucceeded:
-PackageFailed:
+PkgStarted:
+PkgSucceeded:
+PkgFailed:
 
 	The package build status event classes are a bit higher level.  That
 is, they reflect the overall build status of a given package as a whole, without
@@ -20,8 +22,6 @@ the package which failed, in the usual form (i.e. content/glibc-2.3.1-r0).
 
 
 TODO:
-TaskStart
-PackageStart
 UnsatisfiedDep
 RecursiveDep
 MultipleProviders
diff --git a/doc/TODO b/doc/TODO
index 8b483f2f4..244414455 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -43,20 +43,6 @@ TODO:
 	    in the parser code.  In this way, we can more easily facilitate
 	    builds of src.rpms, .dsc's, et cetera.
 
-[.] Event handling
-	[x] event handling core
-	[x] oe/parse.py
-		[x] addevent declaration for .oe files.
-	[x] handle 'event' flag from addevent in oemake/oebuild
-	[.] oemake
-		[ ] default event handlers
-		[x] event declarations
-		[ ] event firing
-	[.] oebuild
-		[ ] default event handlers
-		[x] event declarations
-		[x] event firing
-
 [.] oemaked
 	[x] Autobuilder daemon, monitors files and/or directories
 	    For changes, and runs oemake when appropriate.