diff options
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml')
| -rw-r--r-- | en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml | 242 |
1 files changed, 113 insertions, 129 deletions
diff --git a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml index 4be1c5afae..03aa4ce849 100644 --- a/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml +++ b/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml @@ -1288,9 +1288,9 @@ Fetching 133 new ports or files... done.</screen> </listitem> <listitem> - <para>A quick way of getting bug fixes. Any given commit is - just as likely to introduce new bugs as to fix existing - ones.</para> + <para>A quick way of getting bug fixes. Any given commit + is just as likely to introduce new bugs as to fix + existing ones.</para> </listitem> <listitem> @@ -1333,50 +1333,37 @@ Fetching 133 new ports or files... done.</screen> one of the following methods:</para> <orderedlist> - <indexterm> - <primary>Subversion</primary> - </indexterm> - <indexterm> - <primary><command>cron</command></primary> - </indexterm> - <indexterm> - <primary>-CURRENT</primary> - <secondary>Syncing with - <application>Subversion</application> - </secondary> - </indexterm> - <indexterm> - <primary>-CURRENT</primary> - <secondary>Syncing with - <application>CTM</application> - </secondary> - </indexterm> - <listitem> - <para>Use <link linkend="svn">svn</link> to check out - the desired development or release branch. This is - the recommended method, providing access to &os; - development as it occurs. Checkout the -CURRENT - code from the <literal>head</literal> branch of one - of the <link linkend="svn-mirrors">Subversion mirror + <para>Use <link + linkend="svn">svn</link><indexterm> + <primary>Subversion</primary> + </indexterm> + <indexterm> + <primary>-CURRENT</primary> + <secondary>Syncing with + <application>Subversion</application></secondary> + </indexterm> + to check out the desired development or release + branch. This is the recommended method, providing + access to &os; development as it occurs. Checkout + the -CURRENT code from the <literal>head</literal> + branch of one of the <link + linkend="svn-mirrors">Subversion mirror sites</link>. Due to the size of the repository, it is recommended that only desired subtrees be checked out.</para> </listitem> <listitem> - <indexterm> - <primary>-CURRENT</primary> - <secondary>Syncing with CTM</secondary> - </indexterm> - <para>Use the <application><link - linkend="ctm">CTM</link></application> facility. - If you have bad connectivity such as high price - connections or only email access, + linkend="ctm">CTM</link></application><indexterm> + <primary>-CURRENT</primary> + <secondary>Syncing with CTM</secondary> + </indexterm> facility. If you have bad connectivity + such as high price connections or only email access, <application>CTM</application> is an option, but it - is not as reliable as <application><link - linkend="svn">Subversion</link></application>. + is not as reliable as <application> + <link linkend="svn">Subversion</link></application>. For this reason, <application><link linkend="svn">Subversion</link></application> is the recommended method for any system with @@ -1393,11 +1380,11 @@ Fetching 133 new ports or files... done.</screen> compile just a subset is almost guaranteed to cause problems.</para> - <indexterm> - <primary>-CURRENT</primary> - <secondary>compiling</secondary> - </indexterm> - <para>Before compiling &os.current;, read + <para>Before compiling + &os.current;<indexterm> + <primary>-CURRENT</primary> + <secondary>compiling</secondary> + </indexterm>, read <filename>/usr/src/Makefile</filename> very carefully. <link linkend="makeworld">Install a new kernel and rebuild the world</link> the first time through as part @@ -1524,27 +1511,22 @@ Fetching 133 new ports or files... done.</screen> already running a previous release of &os;:</para> <orderedlist> - <indexterm> - <primary>Subversion</primary> - </indexterm> - <indexterm> - <primary><command>cron</command></primary> - </indexterm> - <indexterm> - <primary>-STABLE</primary> - <secondary>syncing with - <application>Subversion</application></secondary> - </indexterm> - <listitem> - <para>Use <link linkend="svn">svn</link> to check out - the desired development or release branch. This is - the recommended method, providing access to &os; - development as it occurs. Branch names include - <literal>head</literal> for the current development - head, and branches identified in <ulink - url="&url.base;/releng/">the release engineering - page</ulink>, such as <literal>stable/9</literal> + <para>Use <link linkend="svn">svn</link><indexterm> + <primary>Subversion</primary> + + </indexterm> to check out the desired development or + release branch. This is the recommended method, + providing access to &os; development as it occurs. + Branch names include <literal>head</literal> for the + current development head, and branches identified in + <ulink url="&url.base;/releng/">the release + engineering page</ulink>, such as + <literal>stable/9</literal><indexterm> + <primary>-STABLE</primary> + <secondary>syncing with + <application>Subversion</application></secondary> + </indexterm> or <literal>releng/9.0</literal>. URL prefixes for <application>Subversion</application> checkout of the base system are shown in <link @@ -1556,29 +1538,25 @@ Fetching 133 new ports or files... done.</screen> </listitem> <listitem> - <indexterm> - <primary>-STABLE</primary> - <secondary>syncing with CTM</secondary> - </indexterm> - <para>Consider using <application><link - linkend="ctm">CTM</link></application> if you do - not have a fast connection to the Internet.</para> + linkend="ctm">CTM</link></application><indexterm> + <primary>-STABLE</primary> + <secondary>syncing with CTM</secondary> + </indexterm> if you do not have a fast connection to + the Internet.</para> </listitem> </orderedlist> </listitem> <listitem> - <indexterm> - <primary>-STABLE</primary> - <secondary>compiling</secondary> - </indexterm> - - <para>Before compiling &os.stable;, read - <filename>/usr/src/Makefile</filename> carefully. <link - linkend="makeworld">Install a new kernel and rebuild - the world</link> the first time through as part of the - upgrading process. Read &a.stable; and + <para>Before compiling &os.stable;<indexterm> + <primary>-STABLE</primary> + <secondary>compiling</secondary> + </indexterm>, read + <filename>/usr/src/Makefile</filename> carefully. + <link linkend="makeworld">Install a new kernel and + rebuild the world</link> the first time through as part + of the upgrading process. Read &a.stable; and <filename>/usr/src/UPDATING</filename> to keep up-to-date on other bootstrapping procedures that sometimes become necessary on the road to the next @@ -1732,12 +1710,12 @@ Fetching 133 new ports or files... done.</screen> help about synchronizing to a newer version.</para> <para>Updating the system from source is a more subtle process - than it might initially seem to be, and the &os; developers have - found it necessary over the years to change the recommended - approach fairly dramatically as new kinds of unavoidable - dependencies come to light. The rest of this section - describes the rationale behind the currently recommended - upgrade sequence.</para> + than it might initially seem to be, and the &os; developers + have found it necessary over the years to change the + recommended approach fairly dramatically as new kinds of + unavoidable dependencies come to light. The rest of this + section describes the rationale behind the currently + recommended upgrade sequence.</para> <para>Any successful update sequence must deal with the following issues:</para> @@ -1871,11 +1849,12 @@ Fetching 133 new ports or files... done.</screen> <para><command>make <maketarget>delete-old</maketarget></command></para> - <para>This target deletes old (obsolete) files. This is important - because sometimes they cause problems if left on the disk, for - example the presence of the old <filename>utmp.h</filename> - causes problems in some ports when the new - <filename>utmpx.h</filename> is installed.</para> + <para>This target deletes old (obsolete) files. This is + important because sometimes they cause problems if left on + the disk, for example the presence of the old + <filename>utmp.h</filename> causes problems in some ports + when the new <filename>utmpx.h</filename> is + installed.</para> </listitem> <listitem> @@ -1886,10 +1865,11 @@ Fetching 133 new ports or files... done.</screen> </listitem> <listitem> - <para><command>make <maketarget>delete-old-libs</maketarget></command></para> + <para><command>make + <maketarget>delete-old-libs</maketarget></command></para> - <para>Remove any obsolete libraries to avoid conflicts with newer - ones. Make sure that all ports have been rebuilt + <para>Remove any obsolete libraries to avoid conflicts with + newer ones. Make sure that all ports have been rebuilt before old libraries are removed.</para> </listitem> </orderedlist> @@ -2660,27 +2640,28 @@ Script done, …</screen> <primary>Deleting obsolete files and directories</primary> </indexterm> - <para>As a part of the &os; development lifecycle, files and their - contents occasionally become obsolete. This may be because - functionality is implemented elsewhere, the version number of - the library has changed, or it was removed from the system - entirely. This includes old files, libraries, and directories, - which should be removed when updating the system. The benefit - is that the system is not cluttered with old files which take up - unnecessary space on the storage and backup media. - Additionally, if the old library has a security or stability - issue, the system should be updated to the newer library to keep - it safe and to prevent crashes caused by the old library. - Files, directories, and libraries which are considered obsolete - are listed in <filename>/usr/src/ObsoleteFiles.inc</filename>. - The following instructions should be used to remove obsolete - files during the system upgrade process.</para> - - <para>After the <command>make - <maketarget>installworld</maketarget></command> - and the subsequent <command>mergemaster</command> have finished - successfully, check for obsolete files and libraries as - follows:</para> + <para>As a part of the &os; development lifecycle, files and + their contents occasionally become obsolete. This may be + because functionality is implemented elsewhere, the version + number of the library has changed, or it was removed from the + system entirely. This includes old files, libraries, and + directories, which should be removed when updating the system. + The benefit is that the system is not cluttered with old files + which take up unnecessary space on the storage and backup + media. Additionally, if the old library has a security or + stability issue, the system should be updated to the newer + library to keep it safe and to prevent crashes caused by the + old library. Files, directories, and libraries which are + considered obsolete are listed in + <filename>/usr/src/ObsoleteFiles.inc</filename>. The + following instructions should be used to remove obsolete files + during the system upgrade process.</para> + + <para>After the + <command>make <maketarget>installworld</maketarget></command> + and the subsequent <command>mergemaster</command> have + finished successfully, check for obsolete files and libraries + as follows:</para> <screen>&prompt.root; <userinput>cd /usr/src</userinput> &prompt.root; <userinput>make check-old</userinput></screen> @@ -2724,9 +2705,9 @@ Script done, …</screen> <title>Warning</title> <para>Deleting obsolete files will break applications that - still depend on those obsolete files. This is especially true - for old libraries. In most cases, the programs, ports, or - libraries that used the old library need to be recompiled + still depend on those obsolete files. This is especially + true for old libraries. In most cases, the programs, ports, + or libraries that used the old library need to be recompiled before <command>make <maketarget>delete-old-libs</maketarget></command> is executed.</para> @@ -2734,28 +2715,29 @@ Script done, …</screen> <para>Utilities for checking shared library dependencies are available from the Ports Collection in - <filename role="package">sysutils/libchk</filename> or <filename + <filename role="package">sysutils/libchk</filename> or + <filename role="package">sysutils/bsdadminscripts</filename>.</para> - <para>Obsolete shared libraries can conflict with newer libraries, - causing messages like these:</para> + <para>Obsolete shared libraries can conflict with newer + libraries, causing messages like these:</para> <screen>/usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libtiff.so, may conflict with libz.so.5 /usr/bin/ld: warning: librpcsvc.so.4, needed by /usr/local/lib/libXext.so, may conflict with librpcsvc.so.5</screen> - <para>To solve these problems, determine which port installed the - library:</para> + <para>To solve these problems, determine which port installed + the library:</para> <screen>&prompt.root; <userinput>pkg_info -W /usr/local/lib/libtiff.so</userinput> /usr/local/lib/libtiff.so was installed by package tiff-3.9.4 &prompt.root; <userinput>pkg_info -W /usr/local/lib/libXext.so</userinput> /usr/local/lib/libXext.so was installed by package libXext-1.1.1,1</screen> - <para>Then deinstall, rebuild and reinstall the port. <filename - role="package">ports-mgmt/portmaster</filename> can be used to - automate this process. After all ports are rebuilt and no - longer use the old libraries, delete the old libraries using the - following command:</para> + <para>Then deinstall, rebuild and reinstall the port. + <filename role="package">ports-mgmt/portmaster</filename> can + be used to automate this process. After all ports are rebuilt + and no longer use the old libraries, delete the old libraries + using the following command:</para> <screen>&prompt.root; <userinput>make delete-old-libs</userinput></screen> @@ -2818,7 +2800,9 @@ Script done, …</screen> <qandaentry> <question> <para>My compile failed with lots of - signal 11<indexterm><primary>signal 11</primary></indexterm> + signal 11<indexterm> + <primary>signal 11</primary> + </indexterm> (or other signal number) errors. What happened?</para> </question> |