Opened 16 years ago
Last modified 6 years ago
#16061 new defect
Update port.1 man page for clearer description of -f and the state file
Reported by: | blb@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | MacPorts Future |
Component: | base | Version: | 1.6.0 |
Keywords: | port man page | Cc: | jmroot (Joshua Root), vinc17@… |
Port: |
Description
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).
Attachments (1)
Change History (5)
Changed 16 years ago by blb@…
Attachment: | port.1.diff added |
---|
comment:1 Changed 16 years ago by tobypeterson
Milestone: | MacPorts base bugs → MacPorts Future |
---|
Milestone MacPorts base bugs deleted
comment:2 Changed 16 years ago by jmroot (Joshua Root)
Cc: | jmr@… added |
---|
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
comment:4 Changed 15 years ago by jmroot (Joshua Root)
"allows actions from fetch through destroot to be run when the port is installed and up to date" no longer applies after r50490.
Note: See
TracTickets for help on using
tickets.
port.1 diff