deactivate hack in PortfileRecipes?

[Leo Singer]

On Mar 5, 2013, at 8:21 AM, Ryan Schmidt <ryandesign at macports.org> wrote:

> On Mar 5, 2013, at 04:34, Joshua Root wrote:
>> On 2013-3-5 11:32 , Leo Singer wrote:
>>> I was wondering if someone who is very comfortable with the 'deactivate hack' would please post a code snippet and line-by-line explanation in the Wiki under <https://trac.macports.org/wiki/PortfileRecipes>?
>> 
>> I would hope nobody is particularly comfortable with it. It's referred
>> to as a hack for a reason, so it's not something we really want to
>> encourage.
>> 
>> 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.

Oh, I already added replaced_by to the port that I made obsolete, in this case py-novas_py. In the Portfile that replaces it,

https://trac.macports.org/browser/trunk/dports/python/py-novas/Portfile

should I just remove the deactivate hack, the pre-activate stage?