aboutsummaryrefslogtreecommitdiff
path: root/zh_TW.Big5/books/developers-handbook/policies/chapter.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'zh_TW.Big5/books/developers-handbook/policies/chapter.sgml')
-rw-r--r--zh_TW.Big5/books/developers-handbook/policies/chapter.sgml60
1 files changed, 30 insertions, 30 deletions
diff --git a/zh_TW.Big5/books/developers-handbook/policies/chapter.sgml b/zh_TW.Big5/books/developers-handbook/policies/chapter.sgml
index dfad380a53..87e5ed6bf9 100644
--- a/zh_TW.Big5/books/developers-handbook/policies/chapter.sgml
+++ b/zh_TW.Big5/books/developers-handbook/policies/chapter.sgml
@@ -18,14 +18,14 @@
</chapterinfo>
<title>Source Tree Guidelines and Policies</title>
-
+
<para>This chapter documents various guidelines and policies in force for
the FreeBSD source tree.</para>
-
+
<sect1 id="policies-maintainer">
<title><makevar>MAINTAINER</makevar> on Makefiles</title>
<indexterm><primary>ports maintainer</primary></indexterm>
-
+
<para>If a particular portion of the FreeBSD distribution is being
maintained by a person or group of persons, they can communicate this
fact to the world by adding a
@@ -36,7 +36,7 @@
source tree.</para>
<para>The semantics of this are as follows:</para>
-
+
<para>The maintainer owns and is responsible for that code. This means
that he is responsible for fixing bugs and answering problem reports
pertaining to that piece of the code, and in the case of contributed
@@ -54,7 +54,7 @@
does not have to be a committer and it can easily be a group of
people.</para>
</sect1>
-
+
<sect1 id="policies-contributed">
<sect1info>
<authorgroup>
@@ -72,9 +72,9 @@
</sect1info>
<title>Contributed Software</title>
-
+
<indexterm><primary>contributed software</primary></indexterm>
-
+
<para>Some parts of the FreeBSD distribution consist of software that is
actively being maintained outside the FreeBSD project. For historical
reasons, we call this <emphasis>contributed</emphasis> software. Some
@@ -111,7 +111,7 @@
revision 1.1.x.x. The repository bloat impact from a single character
change can be rather dramatic.</para>
</note>
-
+
<para>The <application>Tcl</application> embedded programming
language will be used as example of how this model works:</para>
@@ -146,7 +146,7 @@
ahead and hope it <quote>works out</quote>. CVS is not forgiving of
import accidents and a fair amount of effort is required to back out
major mistakes.</para>
-
+
<para>Because of the previously mentioned design limitations with CVS's
vendor branches, it is required that <quote>official</quote> patches from
the vendor be applied to the original distributed sources and the result
@@ -161,7 +161,7 @@
interest to FreeBSD in order to save space. Files containing copyright
notices and release-note kind of information applicable to the remaining
files shall <emphasis>not</emphasis> be removed.</para>
-
+
<para>If it seems easier, the <command>bmake</command>
<filename>Makefile</filename>s can be produced from the dist tree
automatically by some utility, something which would hopefully make it
@@ -173,27 +173,27 @@
<para>In the <filename>src/contrib/tcl</filename> level directory, a file
called <filename>FREEBSD-upgrade</filename> should be added and it
should state things like:</para>
-
+
<itemizedlist>
<listitem>
<para>Which files have been left out.</para>
</listitem>
-
+
<listitem>
<para>Where the original distribution was obtained from and/or the
official master site.</para>
</listitem>
-
+
<listitem>
<para>Where to send patches back to the original authors.</para>
</listitem>
-
+
<listitem>
<para>Perhaps an overview of the FreeBSD-specific changes that have
been made.</para>
</listitem>
</itemizedlist>
-
+
<para>However, please do not import <filename>FREEBSD-upgrade</filename>
with the contributed source. Rather you should <command>cvs add
FREEBSD-upgrade ; cvs ci</command> after the initial import. Example
@@ -207,7 +207,7 @@ official-patch versions must be imported. Please remember to import with
For the import of GNU cpio 2.4.2, the following files were removed:
- INSTALL cpio.info mkdir.c
+ INSTALL cpio.info mkdir.c
Makefile.in cpio.texi mkinstalldirs
To upgrade to a newer version of cpio, when it is available:
@@ -245,7 +245,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<para>It might occasionally be necessary to include an encumbered file in
the FreeBSD source tree. For example, if a device requires a small
piece of binary code to be loaded to it before the device will operate,
- and we do not have the source to that code, then the binary file is said
+ and we do not have the source to that code, then the binary file is said
to be encumbered. The following policies apply to including encumbered
files in the FreeBSD source tree.</para>
@@ -268,7 +268,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
</listitem>
<listitem>
- <para>Any encumbered file requires specific approval from the
+ <para>Any encumbered file requires specific approval from the
<ulink url="&url.articles.contributors;/staff-core.html">Core team</ulink> before it is added to the
CVS repository.</para>
</listitem>
@@ -279,7 +279,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
</listitem>
<listitem>
- <para>The entire module should be kept together. There is no point in
+ <para>The entire module should be kept together. There is no point in
splitting it, unless there is code-sharing with non-encumbered
code.</para>
</listitem>
@@ -299,9 +299,9 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
</listitem>
<listitem>
- <para>Should always be in <filename>LINT</filename>, but the
+ <para>Should always be in <filename>LINT</filename>, but the
<ulink url="&url.articles.contributors;/staff-core.html">Core team</ulink> decides per case if it
- should be commented out or not. The
+ should be commented out or not. The
<ulink url="&url.articles.contributors;/staff-core.html">Core team</ulink> can, of course, change
their minds later on.</para>
</listitem>
@@ -322,7 +322,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<para>The <ulink url="&url.articles.contributors;/staff-core.html">Core team</ulink> decides if
the code should be part of <command>make world</command>.</para>
</listitem>
-
+
<listitem>
<indexterm><primary>release engineer</primary></indexterm>
<para>The <ulink url="&url.articles.contributors;/staff-who.html">Release Engineer</ulink>
@@ -332,7 +332,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
</listitem>
</orderedlist>
</sect1>
-
+
<sect1 id="policies-shlib">
<sect1info>
<authorgroup>
@@ -361,26 +361,26 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
the release version of the software.</para>
<para>The three principles of shared library building are:</para>
-
+
<itemizedlist>
<listitem>
<para>Start from <literal>1.0</literal></para>
</listitem>
-
+
<listitem>
<para>If there is a change that is backwards compatible, bump minor
number (note that ELF systems ignore the minor number)</para>
</listitem>
-
+
<listitem>
<para>If there is an incompatible change, bump major number</para>
</listitem>
</itemizedlist>
-
+
<para>For instance, added functions and bugfixes result in the minor
version number being bumped, while deleted functions, changed function
call syntax, etc. will force the major version number to change.</para>
-
+
<para>Stick to version numbers of the form major.minor
(<replaceable>x</replaceable>.<replaceable>y</replaceable>). Our a.out
dynamic linker does not handle version numbers of the form
@@ -396,7 +396,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<replaceable>libfoo.so.3</replaceable>.<replaceable>(anything &gt;=
3)</replaceable>.<replaceable>(highest
available)</replaceable>.</para>
-
+
<note>
<para><command>ld.so</command> will always use the highest
<quote>minor</quote> revision. For instance, it will use
@@ -409,7 +409,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
numbers at all. However, one should still specify a major and minor
version number as our <filename>Makefile</filename>s <quote>do the right thing</quote>
based on the type of system.</para>
-
+
<para>For non-port libraries, it is also our policy to change the shared
library version number only once between releases. In addition, it is
our policy to change the major shared library version number only once