Sun May 5 21:26:37 2013 UTC ()

Added sgi-free-software-b-v2.0 to DEFAULT_ACCEPTABLE(*) and added this file
(files.xml) to the list of files to edit in the case of adding another
DEFAULT_ACCEPTABLE license.

(*) http://www.gnu.org/licenses/license-list.en.html#SGIFreeB


(rodent)

diff -r1.118 -r1.119 pkgsrc/doc/guide/files/fixes.xml

--- pkgsrc/doc/guide/files/fixes.xml 2013/04/21 11:33:55 1.118
+++ pkgsrc/doc/guide/files/fixes.xml 2013/05/05 21:26:37 1.119

 @@ -1,14 +1,14 @@
-<!-- $NetBSD: fixes.xml,v 1.118 2013/04/21 11:33:55 rodent Exp $ -->
+<!-- $NetBSD: fixes.xml,v 1.119 2013/05/05 21:26:37 rodent Exp $ -->
 <chapter id="fixes"> <?dbhtml filename="fixes.html"?>
 <title>Making your package work</title>
 <sect1 id="general-operation">
   <title>General operation</title>
   <sect2 id="portability-of-packages">
     <title>Portability of packages</title>
     <para>One appealing feature of pkgsrc is that it runs on many
     different platforms. As a result, it is important to ensure,
     where possible, that packages in pkgsrc are portable. This
 @@ -147,26 +147,27 @@ INTERACTIVE_STAGE=      configure instal
 	lucent
 	miros
 	mit
 	mpl-1.0 mpl-1.1 mpl-2.0
 	mplusfont
 	ofl-v1.0 ofl-v1.1
 	original-bsd modified-bsd 2-clause-bsd
 	php
 	png-license
 	postgresql-license
 	public-domain
 	python-software-foundation
 	qpl-v1.0
 	sgi-free-software-b-v2.0
 	sleepycat-public
 	unlicense
 	x11
 	zlib
 	zpl
     </programlisting>
     </para>
     <para>The license tag mechanism is intended to address
     copyright-related issues surrounding building, installing and
     using a package, and not to address redistribution issues (see
     <varname>RESTRICTED</varname> and
     <varname>NO_SRC_ON_FTP</varname>, etc.).
 @@ -204,26 +205,27 @@ LICENSE=        xv-license
     that license:</para>
     <programlisting>
 ACCEPTABLE_LICENSES+=xv-license
     </programlisting>
     <para>When adding a package with a new license, the following steps
     are required:</para>
     <orderedlist>
     <listitem><para>Check if the file can avoid the -license filename tag as described above by referencing <ulink url="http://www.gnu.org/licenses/license-list.html">Various Licenses and Comments about Them</ulink> and <ulink url="http://opensource.org/licenses/alphabetical">Licenses by Name | Open Source Initiative</ulink>.  If this is the case, additionally add the license filename to:</para>
     <itemizedlist>
     <listitem><para>DEFAULT_ACCEPTABLE_LICENSES in <filename>pkgsrc/mk/license.mk</filename></para></listitem>
     <listitem><para>default_acceptable_licenses in <filename>pkgsrc/pkgtools/pkg_install/files/lib/license.c</filename></para></listitem>
     <listitem><para>the ACCEPTABLE_LICENSES list in <filename>pkgsrc/doc/guide/files/fixes.xml</filename></para></listitem>
     </itemizedlist>
     <para>with the proper syntax as demonstrated in those files, respectively.</para></listitem>
     <listitem><para>The license text should be added to <filename>pkgsrc/licenses</filename> for displaying.  A list of known licenses can be seen in this directory.</para></listitem>
     </orderedlist>
     <para>When the license changes (in a way other than formatting),
     please make sure that the new license has a different name (e.g.,
     append the version number if it exists, or the date).  Just
     because a user told pkgsrc to build programs under a previous
     version of a license does not mean that pkgsrc should build
     programs under the new licenses.  The higher-level point is that
     pkgsrc does not evaluate licenses for reasonableness; the only
     test is a mechanistic test of whether a particular text has been
     approved by either of two bodies.</para>