| 1 |
On Wed, Sep 14, 2005 at 06:53:28PM +0200, Grobian wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> Brian Harring wrote: |
| 5 |
> >Clarifying/rephrasing; pre/post merge triggers will basically be funcs |
| 6 |
> >hooked to run at certain phases. Calling a script could be done, but |
| 7 |
> >if it's python code it's calling it should be a loaded module imo, |
| 8 |
> >rather then the inneficient spawning of a new python interpretter... |
| 9 |
> |
| 10 |
> Ok, I think we want the same ;) The functionality could be part of some |
| 11 |
> "prefixUtility" module perhaps? |
| 12 |
Don't care much name wise, just would have to be defined in the config |
| 13 |
as a trigger. |
| 14 |
|
| 15 |
The reasoning pretty much comes down to being able to shove all arch |
| 16 |
specific crap out of the core, and into pluggable chunks that are |
| 17 |
loaded by configuration settings. |
| 18 |
~harring |
Archives