Explain how to update the currently installed ports.

PR:		25497
Submitted by:	Mike Meyer <mwm@mired.org>
Approved by:	nik
This commit is contained in:
Dima Dorfman 2001-03-13 23:16:39 +00:00
parent c3a09aa491
commit 0689c7fbc2
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8998
2 changed files with 70 additions and 2 deletions

View file

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.152 2001/03/13 01:22:20 dd Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.153 2001/03/13 01:26:08 dd Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -4894,6 +4894,40 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
</answer>
</qandaentry>
<qandaentry>
<question id="ports-update">
<para>I updated the sources, now how do I update my installed
ports?</para>
</question>
<answer>
<para>Unfortunately, there is no easy way to update installed
ports. The <command>pkg_version</command> command can be used
to generate a script that will update the installed ports with
a newer version in the ports tree:</para>
<screen>&prompt.root; <userinput>pkg_version <option>-c</option> > <replaceable>/tmp/myscript</replaceable></userinput></screen>
<para>The output script <emphasis>must</emphasis> be edited by
hand before you use it. Current versions of
<command>pkg_version</command> force this by inserting an
<command>exit</command> at the beginning of the script.</para>
<para>You should save the output of the script, as it will note
packages that depend on the one that has been udpated. These
may or may not need to be updated as well. The usual case where
they need to be updated is that a shared library has changed
version numbers, so the ports that used that library need to be
rebuilt to use the new version.</para>
<para>If your system is up full time, the &man.periodic.8 system
can be used to generate a weekly list of ports that might need
updating by setting
<literal>weekly_status_pkg_enable="YES"</literal> in
<filename>/etc/periodic.conf</filename>.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>

View file

@ -11,7 +11,7 @@
<corpauthor>The FreeBSD Documentation Project</corpauthor>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.152 2001/03/13 01:22:20 dd Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.153 2001/03/13 01:26:08 dd Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -4894,6 +4894,40 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
</answer>
</qandaentry>
<qandaentry>
<question id="ports-update">
<para>I updated the sources, now how do I update my installed
ports?</para>
</question>
<answer>
<para>Unfortunately, there is no easy way to update installed
ports. The <command>pkg_version</command> command can be used
to generate a script that will update the installed ports with
a newer version in the ports tree:</para>
<screen>&prompt.root; <userinput>pkg_version <option>-c</option> > <replaceable>/tmp/myscript</replaceable></userinput></screen>
<para>The output script <emphasis>must</emphasis> be edited by
hand before you use it. Current versions of
<command>pkg_version</command> force this by inserting an
<command>exit</command> at the beginning of the script.</para>
<para>You should save the output of the script, as it will note
packages that depend on the one that has been udpated. These
may or may not need to be updated as well. The usual case where
they need to be updated is that a shared library has changed
version numbers, so the ports that used that library need to be
rebuilt to use the new version.</para>
<para>If your system is up full time, the &man.periodic.8 system
can be used to generate a weekly list of ports that might need
updating by setting
<literal>weekly_status_pkg_enable="YES"</literal> in
<filename>/etc/periodic.conf</filename>.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>