|Commit found by message id
Tue, 13 Dec 2011
[ 07:47:22 dougb ] |
ports-mgmt Manage your ports without external databases or languages
1. Add a feature to allow users to list files that should be
preserved across upgrades.
1. Add a verbose message for cleaning WRKDIRPREFIX
2. Improve the handling of the -F option with packages, especially with
* In update_port() do better at saying what we're launching a child to do
* In post_first_pass() make clear that we are fetch'ing, not building,
* In multiport() call check_fetch_only when we're done
* In the main body add fetch'ed ports to the CUR_DEPS list so that they
are only fetched once.
3. Various typo fixes for the man page.
1. If an update fails in a child port the parent needs to source the
$IPC_SAVE file before it bails out to make sure that various lists are
updated in the parent. This is particularly important for the list(s)
of work already completed, and especially to update PM_NEEDS_UPDATE for
the message of how to resume from the point of failure.
2. For multiple -r, don't add a port to the list of dependents to rebuild
if it was itself specified as a -r port.
3. In parent_exit() run the code to kill background processes if we're
called with a non-zero exit code. That will trigger it (for example)
where the user answers no to the confirmation prompt and is either
using -D, or the generation of the list of valid distfiles did not
4. Until I can revamp the way dependencies are tracked, include all 3
forms of CONFLICTS to make sure we catch alternates.
Number of ports [& non-ports] in this commit: 1
show all files
8 vulnerabilities affecting 14 ports have been reported in the past 14 days
* - modified, not new