On Wed, Sep 14, 2005 at 06:53:28PM +0200, Grobian wrote:
> 
> 
> Brian Harring wrote:
> >Clarifying/rephrasing; pre/post merge triggers will basically be funcs 
> >hooked to run at certain phases.  Calling a script could be done, but 
> >if it's python code it's calling it should be a loaded module imo, 
> >rather then the inneficient spawning of a new python interpretter...
> 
> Ok, I think we want the same ;)  The functionality could be part of some 
> "prefixUtility" module perhaps?
Don't care much name wise, just would have to be defined in the config 
as a trigger.

The reasoning pretty much comes down to being able to shove all arch 
specific crap out of the core, and into pluggable chunks that are 
loaded by configuration settings.
~harring