aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorGuido Falsi <madpilot@FreeBSD.org>2013-09-04 18:20:23 +0000
committerGuido Falsi <madpilot@FreeBSD.org>2013-09-04 18:20:23 +0000
commitfa924c5b6be21899036a119c22f8abd7f25c3cff (patch)
tree0001f374bedd2792e821787ae85fe8d49c2eaab6 /UPDATING
parent642be1b81d8342d3a3323f43bcf5a0bd87a5d363 (diff)
downloadports-fa924c5b6be21899036a119c22f8abd7f25c3cff.tar.gz
ports-fa924c5b6be21899036a119c22f8abd7f25c3cff.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING10
1 files changed, 5 insertions, 5 deletions
diff --git a/UPDATING b/UPDATING
index 5d48f67ac012..c90fd0368e91 100644
--- a/UPDATING
+++ b/UPDATING
@@ -15,11 +15,11 @@ you update your ports collection, before attempting any port upgrades.
Due to this change some major overhauling of the ports tree has
been necessary to move the ports to using that implementation.
- People using pkgng should have little problems, "pkg upgrade"
- will update all sofware to not depend on libivconv anymore, once
- updated packages are available. Please make sure to perform a
- "pkg autoremove" after that and check that libiconv is correctly
- removed by it.
+ People using pkgng binary packages should have little problems,
+ "pkg upgrade" will update all sofware to not depend on libivconv
+ anymore, once updated packages are available. Please make sure to
+ perform a "pkg autoremove" after that and check that libiconv is
+ correctly removed by it.
If you are using ports the update requires some manual intervention.
The following procedure should be followed: