diff options
| author |   Chris Larson <clarson@kergoth.com> | 2003-06-17 19:25:03 +0000 |
|---|---|---|
| committer | Chris Larson <clarson@kergoth.com> | 2003-06-17 19:25:03 +0000 |
| commit | 8ff9fe7c438e3e1cc922e0be92a939296a0d22de (patch) | |
| tree | c41a9f3cb53ada46572150b759ec27a94412b2fe /doc/EVENTS | |
| parent | 988f7a7a1eeb4fcea7f18e9cbb62d51b2528710b (diff) | |
| download | bitbake-8ff9fe7c438e3e1cc922e0be92a939296a0d22de.tar.gz | |
Docu updates per event handling
Diffstat (limited to 'doc/EVENTS')
| -rw-r--r-- | doc/EVENTS | 10 |
1 files changed, 5 insertions, 5 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 |