Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 May 1999 00:29:34 -0500 (CDT)
From:      chris@calldei.com
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   docs/11740: [Patch] doc/en/handbook/patch/chapter.sgml has various bugs (sorry Nik!)
Message-ID:  <199905170529.AAA10314@holly.dyndns.org>

next in thread | raw e-mail | index | archive | help

>Number:         11740
>Category:       docs
>Synopsis:       [Patch] doc/en/handbook/patch/chapter.sgml has various bugs (sorry Nik!)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun May 16 22:30:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Chris Costello
>Release:        FreeBSD 4.0-CURRENT i386
>Organization:
CVS Diff Express, Inc.
>Environment:

Doc tree, CVSupped around 1:00 PM on 17 May.

>Description:

To make the handbook work like Nik's doc tutorial, I've changed many
contractions to their respective expanded meanings.

To keep the documentation up with the software, I have also updated the
__FreeBSD_version table to include the latest -CURRENT changes and the
introduction of 3.2-STABLE.

>How-To-Repeat:

http://www.freebsd.org/handbook/ports.html

>Fix:

Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en/handbook/ports/chapter.sgml,v
retrieving revision 1.17
diff -u -1 -r1.17 chapter.sgml
--- chapter.sgml	1999/05/16 13:28:26	1.17
+++ chapter.sgml	1999/05/17 05:17:37
@@ -119,3 +119,3 @@
 	
-    <para>Fear not, gentle reader, all will become clear (hopefully). Let's
+    <para>Fear not, gentle reader, all will become clear (hopefully). Let us
       see what happens if we try and install a port.  I have chosen
@@ -313,4 +313,4 @@
 	  
-      <para>Let's try something more ambitious now.  Instead of getting a
-	single port skeleton, let's get a whole sub-directory, for example all
+      <para>Let us try something more ambitious now.  Instead of getting a
+	single port skeleton, we will get a whole sub-directory, for example all
 	the database skeletons in the ports collection.  It looks almost the
@@ -764,3 +764,3 @@
 	  used the <option>-fno-strength-reduce</option> option as well.
-	  (Most of the ports don't use <option>-O2</option>).  You
+	  (Most of the ports do not use <option>-O2</option>).  You
 	  <emphasis>should</emphasis> be able to specify the compiler options
@@ -796,3 +796,3 @@
 	  system suddenly stopped compiling it and starting compiling the
-	  <literal>bar</literal> port.  What's going on?</para>
+	  <literal>bar</literal> port.  What is going on?</para>
 	      
@@ -948,3 +948,3 @@
       include.  Please refer to that file for more details on the inner
-      workings of the ports collection.  Even if you don't hack Makefiles
+      workings of the ports collection.  Even if you do not hack Makefiles
       daily, it is well commented, and you will still gain much knowledge from
@@ -1179,3 +1179,3 @@
 	
-	<para>Make sure that there aren't any warnings issued in any of the
+	<para>Make sure that there are not any warnings issued in any of the
 	  <maketarget>package</maketarget> and
@@ -1660,3 +1660,3 @@
 	<para>If the patch is distributed with some other files, such as
-	  documentation, in a gzip'd tarball, you can't just use
+	  documentation, in a gzip'd tarball, you cannot just use
 	  <makevar>PATCHFILES</makevar>.  If that is the case, add the name
@@ -1849,3 +1849,3 @@
 	    some versions of FreeBSD has perl5 as part of the base system
-	    while others don't.)</para>
+	    while others do not.)</para>
 	</sect4>
@@ -1996,3 +1996,3 @@
 	  <filename>/usr/local/lib</filename> and similar to an
-	  <filename>aout</filename> subdirectory.  (If you don't move them out
+	  <filename>aout</filename> subdirectory.  (If you do not move them out
 	  of the way, ELF ports will happily overwrite a.out libraries.) The
@@ -2260,3 +2260,3 @@
 	<makevar>NO_INSTALL_MANPAGES</makevar> is not set, and to
-	<literal>no</literal> otherwise.  You don't have to explicitly define
+	<literal>no</literal> otherwise.  You do not have to explicitly define
 	it unless the default is not suitable for your port.</para>
@@ -2315,3 +2315,3 @@
 	<para>If your port requires Motif, define this variable in the
-	  Makefile.  This will prevent people who don't own a copy of Motif
+	  Makefile.  This will prevent people who do not own a copy of Motif
 	  from even attempting to build it.</para>
@@ -2405,3 +2405,3 @@
 	    <literal>@dircategory</literal> and <literal>@direntry</literal>
-	    statements to files that don't have them.  This is part of my
+	    statements to files that do not have them.  This is part of my
 	    patch:</para>
@@ -2449,3 +2449,3 @@
 	    to use the extra arguments to <command>install-info</command>
-	    because <command>makeinfo</command> can't handle those texinfo
+	    because <command>makeinfo</command> cannot handle those texinfo
 	    sources.  (See <filename>Makefile</filename> and
@@ -2461,3 +2461,3 @@
 	    <command>make</command>; but many <filename>Makefile</filename>s
-	    don't include correct dependencies for info files.  In
+	    do not include correct dependencies for info files.  In
 	    <command>emacs</command>' case, I had to patch the main
@@ -2585,5 +2585,5 @@
 	    <filename>/usr/share/info/dir</filename> and the above command to
-	    create a new info file.  In fact, I'd add the first three lines of
-	    the above patch to <filename>bsd.port.mk</filename> if you (the
-	    porter) wouldn't have to do it in <filename>PLIST</filename> by
+	    create a new info file.  In fact, I would add the first three lines
+	    of the above patch to <filename>bsd.port.mk</filename> if you (the
+	    porter) would not have to do it in <filename>PLIST</filename> by
 	    yourself anyway.</para>
@@ -2645,3 +2645,3 @@
       
-      <para>There are some tricks we haven't mentioned yet about the
+      <para>There are some tricks we have not mentioned yet about the
 	<filename>pkg/</filename> subdirectory that come in handy
@@ -2849,3 +2849,3 @@
 	    license, set the variable <makevar>NO_CDROM</makevar> to a string
-	    describing the reason why.  We will make sure such ports won't go
+	    describing the reason why.  We will make sure such ports will not go
 	    into the CD-ROM come release time.  The distfile and package will
@@ -2856,6 +2856,6 @@
 	  <para>If the resulting package needs to be built uniquely for each
-	    site, or the resulting binary package can't be distributed due to
+	    site, or the resulting binary package cannot be distributed due to
 	    licensing; set the variable <makevar>NO_PACKAGE</makevar> to a
 	    string describing the reason why.  We will make sure such packages
-	    won't go on the ftp site, nor  into the CD-ROM come release time.
+	    will not go on the ftp site, nor  into the CD-ROM come release time.
 	    The distfile will still be included on both however.</para>
@@ -2898,3 +2898,3 @@
 	    
-      <para>If the maintainer asks you to do the upgrade or there isn't any
+      <para>If the maintainer asks you to do the upgrade or there is not any
 	such person to begin with, please make the upgrade and send the
@@ -2971,3 +2971,3 @@
 	    <para><makevar>INSTALL_MAN</makevar> is a command to install
-	      manpages and other documentation (it doesn't compress
+	      manpages and other documentation (it does not compress
 	      anything).</para>
@@ -2998,3 +2998,3 @@
 	<para>Make sure your port honors <makevar>WRKDIRPREFIX</makevar>.
-	  Most ports don't have to worry about this.  In particular, if you
+	  Most ports do not have to worry about this.  In particular, if you
 	  are referring to a <makevar>WRKDIR</makevar> of another port, note
@@ -3033,3 +3033,3 @@
 	  <filename>sys/param.h</filename>.  If you find a system that
-	  doesn't, we would like to know.  Please send mail to the
+	  does not, we would like to know.  Please send mail to the
 	  &a.ports;.</para>
@@ -3044,3 +3044,3 @@
 	    
-	<para>Don't forget to add <literal>-DHAVE_SYS_PARAM_H</literal> to the
+	<para>Do not forget to add <literal>-DHAVE_SYS_PARAM_H</literal> to the
 	  <makevar>CFLAGS</makevar> in the <filename>Makefile</filename> for
@@ -3301,2 +3301,12 @@
 		  </row>
+
+		  <row>
+		    <entry>3.1-STABLE after C++ constructor/destructor order change</entry>
+		    <entry>310002</entry>
+		  </row>
+
+		  <row>
+		    <entry>3.2-STABLE</entry>
+		    <entry>320001</entry>
+		  </row>
 		  
@@ -3306,2 +3316,28 @@
 		  </row>
+
+		  <row>
+		    <entry>4.0-CURRENT after change in dynamic linker handling</entry>
+		    <entry>400001</entry>
+		  </row>
+
+		  <row>
+		    <entry>4.0-CURRENT after C++ constructor/destructor order change</entry>
+		    <entry>400002</entry>
+		  </row>
+
+		  <row>
+		    <entry>4.0-CURRENT after functioning dladdr(3)</entry>
+		    <entry>400003</entry>
+		  </row>
+
+		  <row>
+		    <entry>4.0-CURRENT after newbus</entry>
+		    <entry>400004</entry>
+		  </row>
+
+		  <row>
+		    <entry>4.0-CURRENT after suser(9) API change</entry>
+		    <entry>400005</entry>
+		  </row>
+
 		</tbody>
@@ -3319,3 +3355,3 @@
 	    it infeasible to classify the releases simply by their real
-	    release dates.  If you are making a port now, you don't have to
+	    release dates.  If you are making a port now, you do not have to
 	    worry about old -CURRENTs; they are listed here just for your
@@ -3343,3 +3379,3 @@
 	    <filename>pre.mk</filename>/<filename>post.mk</filename> pair or
-	    <filename>bsd.port.mk</filename> only; don't mix these two.</para>
+	    <filename>bsd.port.mk</filename> only; do not mix these two.</para>
 	</note>
@@ -3553,3 +3589,3 @@
 	  <command>diff</command> to generate patches is fine, but please take
-	  a look at the resulting patches to make sure you don't have any
+	  a look at the resulting patches to make sure you do not have any
 	  unnecessary junk in there.  In particular, diffs between two backup
@@ -3689,3 +3725,3 @@
 	  
-	<para>Make sure you don't use a UID already used by the system or
+	<para>Make sure you do not use a UID already used by the system or
 	  other ports.  This is the current list of UIDs between 50 and
@@ -3736,3 +3772,3 @@
 	<para>The port should respect the <makevar>CFLAGS</makevar> variable.
-	  If it doesn't, please add <literal>NO_PACKAGE=ignores
+	  If it does not, please add <literal>NO_PACKAGE=ignores
 	    cflags</literal> to the <filename>Makefile</filename>.</para>
@@ -3783,6 +3819,6 @@
 
-	<para>Don't copy more copies of the GNU General Public License into
+	<para>Do not copy more copies of the GNU General Public License into
 	  our system, please.</para>
 	
-	<para>Please be careful to note any legal issues! Don't let us
+	<para>Please be careful to note any legal issues! Do not let us
 	  illegally distribute software!</para>
@@ -3843,3 +3879,3 @@
 [do not forget the trailing slash ("/")! 
- if you aren't using MASTER_SITE_* macros]
+ if you are not using MASTER_SITE_* macros]
 MASTER_SITES=  ${MASTER_SITE_XCONTRIB}
@@ -3909,3 +3945,3 @@
 	    
-      <para>If your <makevar>DISTNAME</makevar> doesn't look like that, set
+      <para>If your <makevar>DISTNAME</makevar> does not look like that, set
 	<makevar>PKGNAME</makevar> to something in that format.</para>
@@ -4171,4 +4207,4 @@
 		<entry>Development utilities.  Do not put libraries here just
-		  because they are libraries&mdash;unless they truly don't
-		  belong to anywhere else, they shouldn't be in this
+		  because they are libraries&mdash;unless they truly do not
+		  belong to anywhere else, they should not be in this
 		  category.</entry>
@@ -4253,3 +4289,3 @@
 		<entry>Miscellaneous utilities&mdash;basically things that
-		  doesn't belong to anywhere else.  This is the only category
+		  does not belong to anywhere else.  This is the only category
 		  that should not appear with any other non-virtual category.
@@ -4444,3 +4480,3 @@
 	      instance, an HTML editor should be listed as <literal>www
-		editors</literal>, not the other way around.  Also, you don't
+		editors</literal>, not the other way around.  Also, you do not
 	      need to list <literal>net</literal> when the port belongs to

>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199905170529.AAA10314>