deactivate hack in PortfileRecipes?

[Joshua Root]

On 2013-3-6 03:21 , Ryan Schmidt wrote:
> On Mar 5, 2013, at 04:34, Joshua Root wrote:
>> We should be aiming for a solution in base, perhaps an option like
>> deactivate_conflicting that would trigger the same behaviour for the
>> listed ports as if they were marked as replaced_by the port being activated.
> 
> replaced_by already handles deactivating the replaced port. It's for cases where a port isn't replaced, but rather a particular file moves from one port to another, where the deactivate hack is needed.

I guess I wasn't clear. The hypothetical new option would not behave
exactly like replaced_by, but would cause the same behaviour during the
activate phase when file conflicts are detected.

- Josh