Remove the chapter about "If VuXML still scares you". We do no longer

encourage people to use this approach.

This will be the start of cleaning up the VuXML/portaudit information.

Discussed with:		simon

en_US.ISO8859-1/books/porters-handbook/book.sgml

@@ -7162,33 +7162,6 @@ Reference: <http://www.freebsd.org/ports/portaudit/74a9541d-5d6c-11d8-80e3-00
 &prompt.user; <userinput>packaudit</userinput>
 &prompt.user; <userinput>lynx ~/public_html/portaudit/74a9541d-5d6c-11d8-80e3-0020ed76ef5a.html</userinput></screen>
 	</sect2>
-
-	<sect2 id="security-notify-noxml">
-	  <title>If VuXML still scares you...</title>
-
-	  <para>As an easy alternative to writing VuXML, you may opt to add
-	    a single line to a different file with much simpler syntax,
-	    <filename><envar>PORTSDIR</envar>/security/portaudit-db/database/portaudit.txt</filename>,
-	    which resides within the port <filename
-	    role="package">security/portaudit-db</filename>, and
-	    send a request for review to the Security Officer Team
-	    as described on the <ulink
-	    url="http://www.freebsd.org/security/#how">FreeBSD
-	    Security Information</ulink> page.</para>
-
-	  <para>A line in that file consists of four fields
-	    separated by <literal>|</literal>, a pipe character.
-	    The first field is a &man.pkg.version.1; pattern
-	    expression matching the vulnerable packages.  The second
-	    field contains URLs to relevant information, separated
-	    by space characters.  The third field is a one-line
-	    description of the issue.  The fourth and last field
-	    is the entry's UUID.</para>
-
-	  <para>You may want take a closer look at existing entries in
-	    <filename>portaudit.txt</filename> before adding your
-	    first line to that file.</para>
-	</sect2>
       </sect1>
     </chapter>