Ignore:
Timestamp:
Jan 3, 2015, 12:08:46 AM (4 years ago)
Author:
ryandesign@…
Message:

conflicts_build-1.0.tcl: mention that the deactivation should be forced, and give an example of how to do that, to reduce the occurrence of tickets like #46364 (and countless others about other ports using this portgroup)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/dports/_resources/port1.0/group/conflicts_build-1.0.tcl

    r116727 r130863  
    22# $Id$
    33#
    4 # Copyright (c) 2012, 2014 The MacPorts Project
     4# Copyright (c) 2012, 2014-2015 The MacPorts Project
    55# All rights reserved.
    66#
     
    5353            if {${subport} == ${badport}} {
    5454                ui_error "${subport} cannot be built while another version of ${badport} is active."
    55                 ui_error "Please deactivate the existing copy of ${badport} and try again."
     55                ui_error "Please forcibly deactivate the existing copy of ${badport}, e.g. by running:"
     56                ui_error ""
     57                ui_error "    sudo port -f deactivate ${badport}"
     58                ui_error ""
     59                ui_error "Then try again."
    5660            } else {
    5761                ui_error "${subport} cannot be built while ${badport} is active."
    58                 ui_error "Please deactivate ${badport} and try again."
    59                 ui_error "You can reactivate ${badport} again later."
     62                ui_error "Please forcibly deactivate ${badport}, e.g. by running:"
     63                ui_error ""
     64                ui_error "    sudo port -f deactivate ${badport}"
     65                ui_error ""
     66                ui_error "Then try again. You can reactivate ${badport} again later."
    6067            }
    6168            return -code error "${badport} is active"
Note: See TracChangeset for help on using the changeset viewer.