On Wed, 26 May 2010, Jesse Keating wrote:
On Wed, 2010-05-26 at 16:55 +0200, Alan Franzoni wrote:
> On 5/26/10 4:31 PM, Mike Bonnet wrote:
>> It is intentional. Koji always builds in a single-arch environment.
>> Any multilib setup needs to be done after the build, when assembling a
>> repo or distro. This is what mash is for.
> A maybe-stupid question would be: is there any way to trigger a mash run
> for a mash configruation whenever certain conditions (e.g. new package
> was successfully built) happen? I've found nothing best than a cron
> script by now, but it's a bit clumsy.
Koji is growing support to announce events on a message bus, like qpid.
What that would allow folks to do is setup an event bus and create a
watcher script that watches for specific events like a build being
tagged into a particular tag, which could then trigger the mash call.
i've written a mash plugin for Koji and it works well. I guess I
could work with notting to get it included into mash itself.
I couldn't repair your brakes, so I made your horn louder.