os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Minor word-smith patch which also:

Browse source 
- introduces the term porting

- adds mention of traditional and pkgng formats

Approved by:  gjb (mentor)
This commit is contained in:
Dru Lavigne 2013-10-02 12:38:20 +00:00
parent 3277263509
commit d7031a833c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=42802
1 changed files with 25 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

49
en_US.ISO8859-1/books/handbook/ports/chapter.xml
View file

@ -67,14 +67,14 @@
<procedure>
<step>
<para>Download the software, which might be distributed in
source code format, or as a binary.</para>
<para>Find and download the software, which might be distributed in
source code format or as a binary.</para>
</step>
<step>
<para>Unpack the software from its distribution format
(typically a tarball compressed with &man.compress.1;,
&man.gzip.1;, or &man.bzip2.1;).</para>
<para>Unpack the software from its distribution format. This
is typically a tarball compressed with &man.compress.1;,
&man.gzip.1;, or &man.bzip2.1;.</para>
</step>
<step>
@ -87,8 +87,8 @@
<step>
<para>If the software was distributed in source format,
compile it. This may involve editing a
<filename>Makefile</filename>, or running a
<command>configure</command> script, and other work.</para>
<filename>Makefile</filename> or running a
<command>configure</command> script.</para>
</step>
<step>
@ -96,19 +96,20 @@
</step>
</procedure>
<para>If you are installing a software package that was not
deliberately ported to &os; you may even have to go in and edit
the code to make it work properly.</para>
<para>If the software package was not
deliberately ported, or tested to work, on &os;, the source code may need editing
in order for it to install and run properly. At the time of
this writing, over &os.numports; third-party
applications have been ported to &os;.</para>
<para>&os; provides two technologies which perform these steps for
you. At the time of writing, over &os.numports; third-party
applications are available.</para>
<para>&os; provides two technologies which automate these steps.</para>
<para>A &os; package contains pre-compiled copies of all the
commands for an application, as well as any configuration files
and documentation. A package can be manipulated with &os;
package management commands, such as &man.pkg.add.1;,
&man.pkg.delete.1;, and &man.pkg.info.1;.</para>
and documentation. A package can be manipulated with the traditional &os;
package management commands, such as &man.pkg.add.1;, or using
the newer <application>pkgng</application> commands, such as
<command> pkg install</command>.</para>
<para>A &os; port is a collection of files designed to automate
the process of compiling an application from source code. The
@ -121,12 +122,12 @@
commands.</para>
<para>Both packages and ports understand
<emphasis>dependencies</emphasis>. If &man.pkg.add.1; or the
Ports Collection is used to install an application and a
dependencies. If a package or port
is used to install an application and a
dependent library is not already installed, the library will
automatically be installed first.</para>
<para>While the two technologies are quite similar, packages and
<para>While the two technologies are similar, packages and
ports each have their own strengths. Select the technology that
meets your requirements for installing a particular
application.</para>
@ -145,7 +146,7 @@
applications, such as
<application>Mozilla</application>,
<application>KDE</application>, or
<application>GNOME</application> this can be important,
<application>GNOME</application>, this can be important
on a slow system.</para>
</listitem>
@ -156,7 +157,7 @@
</itemizedlist>
<itemizedlist>
<title>Ports Benefits</title>
<title>Port Benefits</title>
<listitem>
<para>Packages are normally compiled with conservative
@ -184,7 +185,7 @@
<listitem>
<para>The licensing conditions of some software forbid binary
distribution. These must be distributed as source code
distribution. Such software must be distributed as source code
which must be compiled by the end-user.</para>
</listitem>
@ -195,8 +196,8 @@
</listitem>
<listitem>
<para>If you have local patches, you will need the source in
order to apply them.</para>
<para>Source code is needed in
order to apply custom patches.</para>
</listitem>
</itemizedlist>