diff options
| author | Guido Falsi <madpilot@FreeBSD.org> | 2013-09-04 18:20:23 +0000 |
|---|---|---|
| committer | Guido Falsi <madpilot@FreeBSD.org> | 2013-09-04 18:20:23 +0000 |
| commit | fa924c5b6be21899036a119c22f8abd7f25c3cff (patch) | |
| tree | 0001f374bedd2792e821787ae85fe8d49c2eaab6 /UPDATING | |
| parent | 642be1b81d8342d3a3323f43bcf5a0bd87a5d363 (diff) | |
| download | ports-fa924c5b6be21899036a119c22f8abd7f25c3cff.tar.gz ports-fa924c5b6be21899036a119c22f8abd7f25c3cff.zip | |
Fix wording in UPDATING message.
Notes
Notes:
svn path=/head/; revision=326308
Diffstat (limited to 'UPDATING')
| -rw-r--r-- | UPDATING | 10 |
1 files changed, 5 insertions, 5 deletions
@@ -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: |