Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Jan 2010 09:59:29 -0700 (MST)
From:      Warren Block <>
To:        Matthew Seaman <>
Cc:        "b. f." <>,,,, Ion-Mihai Tetcu <>,
Subject:   Re: Dislike the way port conflicts are handled now
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Sun, 17 Jan 2010, Matthew Seaman wrote:

> Ion-Mihai Tetcu wrote:
>> I'd be very happy if I could:
>> - fetch the distfiles, even if I have a conflicting port installed
>> - be able to use portmaster -o to switch from one port to an other one
>>   that conflicts with it.
>> - be able to at least compile a port (eg. for testing) without having
>>   to de-install the current one.
>> I'm all in favor of restoring the old behavior with a switch available
>> to turn on the new one.
> +1
> Although a big fat warning message at fetch or build phase when operating on
> a port with conflicts wouldn't go amiss.

Agreed.  A warning would give time to interrupt a big distfile fetch or 
build without taking that option away by default, or encouraging 
disabling conflict checks altogether.

-Warren Block * Rapid City, South Dakota USA

Want to link to this message? Use this URL: <>