aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorChris Larson <clarson@kergoth.com>2003-06-19 23:30:41 +0000
committerChris Larson <clarson@kergoth.com>2003-06-19 23:30:41 +0000
commitea843a1aa05570afb23a982824320fdb00333ec0 (patch)
tree0c100acd2a93f308e6ab1b76baf6c5ad18fe0ac0 /doc
parent4214c9ead86654a192842af670501f7520bad15c (diff)
downloadbitbake-ea843a1aa05570afb23a982824320fdb00333ec0.tar.gz
Add UnsatisfiedDep info to the event docs, and add a small blurb about event handling.
Diffstat (limited to 'doc')
-rw-r--r--doc/EVENTS15
1 files changed, 14 insertions, 1 deletions
diff --git a/doc/EVENTS b/doc/EVENTS
index 0e7127f9a..a41693b27 100644
--- a/doc/EVENTS
+++ b/doc/EVENTS
@@ -20,9 +20,22 @@ is, they reflect the overall build status of a given package as a whole, without
the task level breakdown. The 'package' attribute is a string which contains
the package which failed, in the usual form (i.e. content/glibc-2.3.1-r0).
+UnsatisfiedDep:
+
+ This event is triggered by oemake whenever an unsatisfied dependency
+is encountered on a package we're attempting to build. It will remove the
+package from the build, and every package that directly or indirectly depends
+on the package that encountered this problem.
+
+Handling:
+
+ Any .oe or .oeclass can register an event handler. It is simply
+'addhandler <variable> [<othervariable> <anothervariable> ...]'. The
+variable in question must be flagged as a block of python code, and, due
+to the way in which it spawns the code, must be indented by an extra tab.
+See the base.oeclass for our base event handler as an example.
TODO:
-UnsatisfiedDep
RecursiveDep
MultipleProviders