svn commit: r47878 - head/en_US.ISO8859-1/books/porters-handbook/porting-dads

Warren Block <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
Author: wblock
Date: Thu Dec 17 01:52:33 2015
New Revision: 47878
URL: https://svnweb.freebsd.org/changeset/doc/47878

Log:
  Whitespace-only fixes, translators please ignore.

Modified:
  head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml

Modified: head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml	Thu Dec 17 01:46:51 2015	(r47877)
+++ head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml	Thu Dec 17 01:52:33 2015	(r47878)
@@ -132,8 +132,9 @@
 	<tbody>
 	  <row>
 	    <entry><varname>ARCH</varname></entry>
-	    <entry>The architecture as returned by <command>uname
-		-m</command> (for example, <literal>i386</literal>)</entry>
+	    <entry>The architecture as returned by
+	      <command>uname -m</command> (for example,
+	      <literal>i386</literal>)</entry>
 	  </row>
 
 	  <row>
@@ -159,8 +160,8 @@
 
 	  <row>
 	    <entry><varname>LOCALBASE</varname></entry>
-	    <entry>The base of the <quote>local</quote> tree (for example,
-	      <literal>/usr/local</literal>)</entry>
+	    <entry>The base of the <quote>local</quote> tree (for
+	      example, <literal>/usr/local</literal>)</entry>
 	  </row>
 
 	  <row>
@@ -216,9 +217,9 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
     <title>Do Things Rationally</title>
 
     <para>The <filename>Makefile</filename> should do things in a
-      simple and reasonable manner.  Making it a couple of lines shorter or
-      more readable is always better.  Examples include using a make
-      <literal>.if</literal> construct instead of a shell
+      simple and reasonable manner.  Making it a couple of lines
+      shorter or more readable is always better.  Examples include
+      using a make <literal>.if</literal> construct instead of a shell
       <literal>if</literal> construct, not redefining
       <buildtarget>do-extract</buildtarget> if redefining
       <varname>EXTRACT*</varname> is enough, and using
@@ -228,10 +229,10 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
 
     <para>If a lot of new code is needed to do something, there may
       already be an implementation of it in
-      <filename>bsd.port.mk</filename>.  While
-      hard to read, there are a great many seemingly-hard problems for
-      which <filename>bsd.port.mk</filename> already provides a
-      shorthand solution.</para>
+      <filename>bsd.port.mk</filename>.  While hard to read, there are
+      a great many seemingly-hard problems for which
+      <filename>bsd.port.mk</filename> already provides a shorthand
+      solution.</para>
   </sect1>
 
   <sect1 xml:id="dads-cc">
@@ -250,9 +251,9 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
       <literal>NO_PACKAGE=ignores either cc or cxx</literal> to the
       <filename>Makefile</filename>.</para>
 
-    <para>Here is an example of a <filename>Makefile</filename> respecting
-      both <varname>CC</varname> and <varname>CXX</varname>.
-      Note the <literal>?=</literal>:</para>
+    <para>Here is an example of a <filename>Makefile</filename>
+      respecting both <varname>CC</varname> and
+      <varname>CXX</varname>.  Note the <literal>?=</literal>:</para>
 
     <programlisting>CC?= gcc</programlisting>
 
@@ -288,8 +289,8 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
       <literal>NO_PACKAGE=ignores cflags</literal> to the
       <filename>Makefile</filename>.</para>
 
-    <para>Here is an example of a <filename>Makefile</filename> respecting
-      <varname>CFLAGS</varname>.  Note the
+    <para>Here is an example of a <filename>Makefile</filename>
+      respecting <varname>CFLAGS</varname>.  Note the
       <literal>+=</literal>:</para>
 
     <programlisting>CFLAGS+= -Wall -Werror</programlisting>
@@ -421,19 +422,18 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
 	  <para><varname>FORBIDDEN</varname> is used for ports that
 	    contain a security vulnerability or induce grave concern
 	    regarding the security of a &os; system with a given port
-	    installed (for example, a reputably insecure program or a program
-	    that provides easily exploitable services).  Mark ports
-	    as <varname>FORBIDDEN</varname> as soon as a
+	    installed (for example, a reputably insecure program or a
+	    program that provides easily exploitable services).  Mark
+	    ports as <varname>FORBIDDEN</varname> as soon as a
 	    particular piece of software has a vulnerability and there
-	    is no released upgrade.  Ideally upgrade ports
-	    as soon as possible when a security vulnerability is
-	    discovered so as to reduce the number of vulnerable &os;
-	    hosts (we like being known for being secure), however
-	    sometimes there is a noticeable time gap between
-	    disclosure of a vulnerability and an updated release of
-	    the vulnerable software.  Do not mark a port
-	    <varname>FORBIDDEN</varname> for any reason other than
-	    security.</para>
+	    is no released upgrade.  Ideally upgrade ports as soon as
+	    possible when a security vulnerability is discovered so as
+	    to reduce the number of vulnerable &os; hosts (we like
+	    being known for being secure), however sometimes there is
+	    a noticeable time gap between disclosure of a
+	    vulnerability and an updated release of the vulnerable
+	    software.  Do not mark a port <varname>FORBIDDEN</varname>
+	    for any reason other than security.</para>
 	</listitem>
 
 	<listitem>
@@ -684,10 +684,10 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD
 	xlink:href="https://wiki.ubuntu.com/DashAsBinSh">here</link>.</para>
 
     <para>Check that headers are included in the
-      <acronym>POSIX</acronym> or man page recommended way.  For example,
-      <filename>sys/types.h</filename> is often forgotten, which is
-      not as much of a problem for &linux; as it is for &os;.</para>
-
+      <acronym>POSIX</acronym> or man page recommended way.  For
+      example, <filename>sys/types.h</filename> is often forgotten,
+      which is not as much of a problem for &linux; as it is for
+      &os;.</para>
   </sect1>
 
   <sect1 xml:id="dads-misc">
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.