[16:39] Hello :) [18:56] *reading job_emit_event* [19:00] wraiden: good luck [19:00] the last person who went in there never came out [19:20] hehe [19:20] i think i have found the point to add the alias handling [19:21] it would be in there, yes [19:21] i think i move the environment construction into an helper as i have to construkt the environment for the job event itself and all aliases that might be set... [19:22] or is it possibe to overwrite the JOB in an already constructed environment ? [19:22] that would make it very easy *G* [19:23] yeah, you can keep setting JOB to overwrite it [19:23] see environ.c [19:23] and it will hold its position as the first env var on the event? [19:24] yes [19:25] see environ_add() [19:25] (provided you go through that function, of course) [19:26] environ_set() calls environ_add() fwiw [19:26] nice and handy *g* [19:38] where does the code actualy block until all jobs that hook into a blocking event are processed? [19:42] the code doesn't block per-se [19:43] job_change_state sets job->blocker to the return value of job_emit_event [19:43] and doesn't change state to the next one, so ends [19:44] event_finished() is what, when an event reaches zero blockers, calls job_change_state to unblock the job [19:45] if i implement the aliases as multiple independent blocking events... [19:45] then i have to check if no other alias event is still blocking [19:45] mhm [19:52] interesting [19:52] yeah you may have to extend things [20:01] if i understand the code right than i can add multiple blocking events to the main jobs event->blocking