[89180] trunk/base/src/port/port-help.tcl

[Ryan Schmidt]

On Jan 20, 2012, at 06:12, cal at macports.org wrote:

> Revision: 89180
>          http://trac.macports.org/changeset/89180
> Author:   cal at macports.org
> Date:     2012-01-20 04:12:12 -0800 (Fri, 20 Jan 2012)
> Log Message:
> -----------
> Add port help rev-upgrade
> 
> Modified Paths:
> --------------
>    trunk/base/src/port/port-help.tcl
> 
> Modified: trunk/base/src/port/port-help.tcl
> ===================================================================
> --- trunk/base/src/port/port-help.tcl	2012-01-20 11:58:11 UTC (rev 89179)
> +++ trunk/base/src/port/port-help.tcl	2012-01-20 12:12:12 UTC (rev 89180)
> @@ -253,6 +253,22 @@
> 
> set porthelp(quit) $porthelp(exit)
> 
> +set porthelp(rev-upgrade) {
> +Scan for broken binaries in the installed ports and rebuild them as needed. Can
> +be run with -y to only report broken ports, but not automatically rebuild them.
> +
> +You normally wouldn't have to run rev-upgrade manually; it is run automatically
> +after each install and upgrade by default. Rev-upgrade doesn't honor package
> +names, e.g.
> +	upgrade outdated
> +will not run rev-upgrade only on outdated, because ports not in outdated might
> +have been broken by upgrade outdated. Rev-upgrade will always run on all your
> +active ports.
> +
> +See man 1 port, section rev-upgrade, and man 5 macports.conf, directives
> +starting with revupgrade_ for configuration and more information.
> +}

I have not used rev-upgrade yet, but reading this description, it sounds like it would introduce a significant delay after upgrading, if I have a lot of ports installed.

I'm also not clear on what the use case is for rev-upgrade. Are we trying to catch cases where maintainers forget to increase the revision of ports to force a rebuild, or are we trying to phase out the practice of manually bumping the revisions for this case?

I'm concerned about what happens when a library version increases, thus triggering rev-upgrade to do its thing in some set of ports, but the packages server is still distributing binaries linked with the old version of the library.