I have created a ticket with the patch as suggested: https://trac.macports.org/ticket/48909
Kind regards. Artur ________________________________________ From: Rainer Müller [rai...@macports.org] Sent: 15 September 2015 19:06 To: Artur Szostak Cc: macports-users Subject: Re: Versions in ports On 2015-09-15 12:18, Artur Szostak wrote: >> If there is any documentation advocating upgrading individual >> ports, or especially documentation advocating downgrading a port, >> please send us the URL so that we can correct the information. > > How about the manpage. When looking at the description of the upgrade > command there is not a single notice or disclaimer that upgrading an > individual port is not recommended because it can lead to problems. I > would also expect it to mention that the standard way to upgrade is > always: port upgrade outdated Sounds like a good improvement. Actually, the next 2.x release will feature a new documentation system with a separate man page for each of the commands. For example, the current trunk versions of the port(1) and port-upgrade(1) man pages can be viewed in the repository [1,2]. If you have an idea how to incorporate this information, you are very welcome to submit patches for the documentation (just text would be okay as well, formatting is the easy part). For the man pages, we switched to AsciiDoc syntax, so editing should be quite easy now. Updating the guide is a bit more cumbersome as it is written in DocBook XML, but the README at [3] has at least some pointers on how to check for syntax errors. Rainer [1] https://svn.macports.org/repository/macports/trunk/base/doc/port.1.txt [2] https://svn.macports.org/repository/macports/trunk/base/doc/port-upgrade.1.txt [3] https://svn.macports.org/repository/macports/trunk/doc-new/ _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
