Update port.1 man page for clearer description of -f and the state file

[blb@…]

Will attach a diff to base/doc/port.1 to clarify the description of the -f option and what it means in regards to the state file (since I misread it in the opposite direction of its meaning).

[blb@…]

port.1 diff

[toby@…]

Milestone MacPorts base bugs deleted

[jmr@…]

Based on my testing on current trunk, -f does not in fact cause port to ignore the state file in this way. However, it:

• causes sync to redownload a daily tarball even if the mod time hasn't changed
• causes selfupdate to rebuild base even if it doesn't appear to be outdated
• causes upgrade to rebuild ports even if they don't appear to be outdated
• causes the unarchive phase to be skipped
• causes fatal_softcontinue to continue instead of exit
• causes clean to remove files in the dist_subdir even if they may not belong to the port being cleaned
• allows actions from fetch through destroot to be run when the port is installed and up to date
• allows a build to continue with different variants than it was started with
• allows ports with files that conflict with what's already there to be activated
• allows ports with dependents to be uninstalled

[vinc17@…]

Cc Me!

[jmr@…]

"allows actions from fetch through destroot to be run when the port is installed and up to date" no longer applies after r50490.