documentation/poky-ref-manual/development.xml: Deleted development chapter

The Development chapter has been emptied out so it is now deleted from
the reference manual.  All relevant topics now reside in the YP
Development Manual.

(From yocto-docs rev: aa30971ea0b23c19e3fefcb48db8aa4c0db8e95e)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 0 insertions, 45 deletions

diff --git a/documentation/poky-ref-manual/development.xml b/documentation/poky-ref-manual/development.xml
deleted file mode 100644
index af8a59cb0c..0000000000
--- a/documentation/poky-ref-manual/development.xml
+++ /dev/null
@@ -1,45 +0,0 @@
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
-[<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
-
-<chapter id="platdev">
-<title>Platform Development with the Yocto Project</title>
-
-    <section id="platdev-appdev">
-    <title>Application Development Using the Yocto Project</title>
-    <para>
-        The Yocto Project supports several methods of application development through which 
-        you can create user-space software designed to run on an embedded device that uses
-        a Yocto Project image, which was developed with the OpenEmbedded build system. 
-        This flexibility allows you to choose the method that works best for you.  
-        This chapter describes each development method.
-    </para>
-
-        <section id="platdev-appdev-srcrev">
-        <title>Development Within Yocto Project for a Package that Uses an External SCM</title>
-
-        <para>
-            If you're working on a recipe that pulls from an external Source Code Manager (SCM), it 
-            is possible to have the OpenEmbedded build system notice new changes added to the 
-            SCM and then build the package that depends on them using the latest version. 
-            This only works for SCMs from which it is possible to get a sensible revision number for changes.
-            Currently, you can do this with Apache Subversion (SVN), Git, and Bazaar (BZR) repositories.
-        </para>
-
-        <para>
-            To enable this behavior, simply add the following to the <filename>local.conf</filename>
-            configuration file found in the 
-            <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>build directory</ulink>:
-            <literallayout class='monospaced'>
-     SRCREV_pn-&lt;PN&gt; = "${AUTOREV}"
-            </literallayout>
-            where <filename>PN</filename> 
-            is the name of the package for which you want to enable automatic source 
-            revision updating.
-        </para>
-        </section>
-    </section>
-</chapter> 
-<!-- 
-vim: expandtab tw=80 ts=4 
--->