svn commit: r42802 - head/en_US.ISO8859-1/books/handbook/ports
Benjamin Kaduk
kaduk at MIT.EDU
Thu Oct 3 02:16:48 UTC 2013
On Wed, 2 Oct 2013, Dru Lavigne wrote:
> Author: dru
> Date: Wed Oct 2 12:38:20 2013
> New Revision: 42802
> URL: http://svnweb.freebsd.org/changeset/doc/42802
>
> Log:
> Minor word-smith patch which also:
>
> - introduces the term porting
>
> - adds mention of traditional and pkgng formats
>
> Approved by: gjb (mentor)
>
> Modified:
> head/en_US.ISO8859-1/books/handbook/ports/chapter.xml
>
> Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml
> ==============================================================================
> --- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Wed Oct 2 11:47:11 2013 (r42801)
> +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Wed Oct 2 12:38:20 2013 (r42802)
>
> <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
I think that the pkgng guys want us to stick to the story that the
application is just 'pkg', and it is the project which is 'pkgng' (so that
we can stop talking about pkgng once it's the standard way of doing
things, and we don't ever end up with 'pkgngng'). So this would probably
be "the historical &os; package management commands, [...] or using the
newer <application>pkg</application> comands".
Baptise, is that right?
-Ben
> + <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
More information about the svn-doc-head
mailing list