[PATCH] system_x11 variant

[Ryan Schmidt]

On Jan 4, 2009, at 15:35, Bryan Blackburn wrote:

>>> Overriding activate causes them to be installed but then
>>> remain inactive, and hence show in 'port installed inactive' as  
>>> well as
>>> possiblity causing confusion for those who use 'port uninstall
>>> inactive'.
>>
>> Ok, so if I nuke those overrides, we should be good then, right?
>
> Right, which I see you've already done.  I'm not sure what the side- 
> effects
> would be from overriding archive like that (beyond it simply not  
> making one
> of course), but overriding active definitely creates confusion.

Is there a way that MacPorts base could prevent ports from overriding  
the activate phase? Don't we already do that for commands like load  
and distfiles? At least that's what it seems to me the following  
output during an install means:

DEBUG: org.macports.load registered provides 'load', a pre-existing  
procedure. Target override will not be provided
DEBUG: org.macports.distfiles registered provides 'distfiles', a pre- 
existing procedure. Target override will not be provided