svn commit: r54728 - head/en_US.ISO8859-1/books/porters-handbook/makefiles

Guangyuan Yang ygy at FreeBSD.org
Thu Dec 3 19:05:39 UTC 2020


Author: ygy
Date: Thu Dec  3 19:05:38 2020
New Revision: 54728
URL: https://svnweb.freebsd.org/changeset/doc/54728

Log:
  Add "education" virtual category to Porter's Handbook.
  
  - The category itself was added to the ports framework in r555738.
  - While there, fix a typo.
  
  PR:		248403
  Submitted by:	PauAmma <pauamma at gundo.com>
  Reviewed by:	adamw, bcr, mat
  Differential Revision:	https://reviews.freebsd.org/D27340

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

Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml	Thu Dec  3 16:35:34 2020	(r54727)
+++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml	Thu Dec  3 19:05:38 2020	(r54728)
@@ -1127,6 +1127,18 @@ PORTEPOCH=	1</programlisting>
 	    </row>
 
 	    <row>
+	      <entry><filename>education</filename>
+		<literal>*</literal></entry>
+	      <entry>Education-related software.</entry>
+	      <entry>This includes applications, utilities, or games
+		primarily or substantially designed to help the user
+		learn a specific topic or study in general.  It also
+		includes course-writing applications, course-delivery
+		applications, and classroom or school management
+		applications.</entry>
+	    </row>
+
+	    <row>
 	      <entry><filename>elisp</filename>
 		<literal>*</literal></entry>
 	      <entry>Emacs-lisp ports.</entry>
@@ -1786,7 +1798,7 @@ PORTEPOCH=	1</programlisting>
 	not have a corresponding subdirectory in the ports tree—
 	or <emphasis>physical</emphasis> categories—those that
 	do.  This section discusses the issues involved in creating a
-	new physical category.  Read it thouroughly before proposing a
+	new physical category.  Read it thoroughly before proposing a
 	new one.</para>
 
       <para>Our existing practice has been to avoid creating a new


More information about the svn-doc-all mailing list