summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-12-09 07:07:42 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-11 14:19:28 +0000
commit644fdc41557f487c671e438f3d8574087b47ec29 (patch)
treef4768cc90ba85696b4876b546d73d5946490c33a
parent55a505805993a2d37a4a448bacf2d90d3fc03169 (diff)
downloadpoky-644fdc41557f487c671e438f3d8574087b47ec29.tar.gz
ref-manual: Edits to bugzilla and deploy class.
Fixed a link in the deploy class. Re-wrote the bugzilla class to be clearer. (From yocto-docs rev: 4bb975a0e12c9d38e941f1cf913c042498f06976) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/ref-manual/ref-classes.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index a5a906d5ac..965302f778 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -291,11 +291,11 @@
291 <title><filename>bugzilla.bbclass</filename></title> 291 <title><filename>bugzilla.bbclass</filename></title>
292 292
293 <para> 293 <para>
294 The <filename>bugzilla</filename> class automatically files bug reports 294 The <filename>bugzilla</filename> class supports setting up an
295 to a Bugzilla instance in response to build failures. 295 instance of Bugzilla in which you can automatically files bug reports
296 This class uses Bugzilla's XML-RPC interface. 296 in response to build failures.
297 Consequently, you need to enable the class in the instance of Bugzilla 297 For this class to work, you need to enable the XML-RPC interface in
298 within which you wish to file reports. 298 the instance of Bugzilla.
299 </para> 299 </para>
300</section> 300</section>
301 301
@@ -529,7 +529,7 @@
529 Recipes that inherit this class should define their own 529 Recipes that inherit this class should define their own
530 <filename>do_deploy</filename> function to copy the files to be 530 <filename>do_deploy</filename> function to copy the files to be
531 deployed to 531 deployed to
532 <link linkend='var-DEPLOY_DIR'><filename>DEPLOYDIR</filename></link>, 532 <link linkend='var-DEPLOYDIR'><filename>DEPLOYDIR</filename></link>,
533 and use <filename>addtask</filename> to add the task at the appropriate 533 and use <filename>addtask</filename> to add the task at the appropriate
534 place, which is usually after <filename>do_compile</filename> or 534 place, which is usually after <filename>do_compile</filename> or
535 <filename>do_install</filename>. 535 <filename>do_install</filename>.