Date: 2 Mar 2001 21:12:25 -0000 From: mwm@mired.org To: FreeBSD-gnats-submit@freebsd.org Subject: docs/25497: [PATCH} There is no answer to the FAQ about updating ports in the FAQ. Message-ID: <20010302211225.12928.qmail@guru.mired.org>
index | next in thread | raw e-mail
>Number: 25497
>Category: docs
>Synopsis: [PATCH} There is no answer to the FAQ about updating ports in the FAQ.
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Mar 02 13:20:03 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Mike Meyer
>Release: FreeBSD 4.2-STABLE i386
>Organization:
Meyer Consulting
>Environment:
freebsd-questions@freebsd.org
>Description:
The question "How do I udpate all my installed ports after supping"
comes up frequently. There's no answer in the FAQ.
>How-To-Repeat:
Hang out in -questions for a while, and watch the questions go by.
>Fix:
Apply the following patch to the faq/book.sgml.
--- /tmp/book.sgml Fri Mar 2 14:36:07 2001
+++ book.sgml Fri Mar 2 15:01:50 2001
@@ -4887,6 +4887,43 @@
</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 udpate
+ installed ports. The <command>pkg_version(1)</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>
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010302211225.12928.qmail>