From 0689c7fbc273a4b3a479aa28e856e7671b1fc7f7 Mon Sep 17 00:00:00 2001 From: Dima Dorfman Date: Tue, 13 Mar 2001 23:16:39 +0000 Subject: [PATCH] Explain how to update the currently installed ports. PR: 25497 Submitted by: Mike Meyer Approved by: nik --- en_US.ISO8859-1/books/faq/book.sgml | 36 +++++++++++++++++++++++++++- en_US.ISO_8859-1/books/faq/book.sgml | 36 +++++++++++++++++++++++++++- 2 files changed, 70 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 9fc8ef0f78..6a8235cbdb 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -11,7 +11,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.152 2001/03/13 01:22:20 dd Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.153 2001/03/13 01:26:08 dd Exp $ 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 + + + + I updated the sources, now how do I update my installed + ports? + + + + Unfortunately, there is no easy way to update installed + ports. The pkg_version command can be used + to generate a script that will update the installed ports with + a newer version in the ports tree: + + &prompt.root; pkg_version > /tmp/myscript + + The output script must be edited by + hand before you use it. Current versions of + pkg_version force this by inserting an + exit at the beginning of the script. + + 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. + + 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 + weekly_status_pkg_enable="YES" in + /etc/periodic.conf. + + diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 9fc8ef0f78..6a8235cbdb 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -11,7 +11,7 @@ The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.152 2001/03/13 01:22:20 dd Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.153 2001/03/13 01:26:08 dd Exp $ 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 + + + + I updated the sources, now how do I update my installed + ports? + + + + Unfortunately, there is no easy way to update installed + ports. The pkg_version command can be used + to generate a script that will update the installed ports with + a newer version in the ports tree: + + &prompt.root; pkg_version > /tmp/myscript + + The output script must be edited by + hand before you use it. Current versions of + pkg_version force this by inserting an + exit at the beginning of the script. + + 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. + + 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 + weekly_status_pkg_enable="YES" in + /etc/periodic.conf. + +