Re: A proposal

David Grimberg <[email protected]> writes:

> Lloyd,
>
> This does sound like a good idea, but I would suggest that instead of
> just one configuration variable, you stayed with the current precedents
> within TMDA and created a variable for each action
> e.g. PENDING_RELEASE_ACTION_HOOK.  That way the external program or
> script wouldn't need to know anything about the actions being passed to
> it as parameters.  It does of course mean that you would have to fill in
> a variable for each action with which you want to perform some external
> operation, but not every one will want to handle each TMDA action
> externally.

Well, I could make four variables, or actually five, taking Ole Wolf's
point about having another action for "confirm" into consideration.  I
just didn't want to do the extra work in patching the code that the five
variables would require.

But I'm willing to do that, if the five-variable idea is preferred
by the tmda community over the single-variable approach.

Does anyone have preferences or further feedback about this?

... and thanks to you and Ole Wolf.


-- 
 Lloyd Zusman
 [email protected]
 God bless you.