On Wed, 2011-10-05 at 10:06 -0700, Jesse Keating wrote: > On Oct 4, 2011, at 10:31 PM, Adam Williamson wrote: > > On Thu, 2011-09-29 at 09:39 -0400, Jesse Keating wrote: > >> On Sep 29, 2011, at 6:22 AM, Nils Philippsen wrote: > >>> > >>> Ahh I'm late. Anyway, that's a side-effect of using the bodhi interface > >>> to manage something in koji then. It'd still be handy if we could use > >>> that for Rawhide so we don't break all dependent things for people who > >>> want to test something else than what we're breaking at the moment. > >> > >> You're thinking of creating a /new/ build target and build tag/root. > >> That's not what bodhi does. > >> > >> Buildroot overrides for the rawhide tags make no sense, as anything > >> built automatically lands in the build root. > > > > So really want they want is a *tag*, not a buildroot override, right? > > > > They can have a tag for Rawhide if they request one, I presume? > > > I don't even know what that would mean. I was thinking of something like the f16-gnome tag the desktop team uses to do big messy GNOME builds in before re-tagging them so they can be submitted as updates. I didn't know all the issues behind that. :) > tl;dr if you're looking for bodhi to allow on-demand creation of > topic-tags for isolating build efforts from rawhide, that's too > expensive of an item to allow a free-for-all at this time, in my > opinion. On demand, no. That's why I said 'if they request one'. I was assuming a manually handled, human-in-the-loop type of 'request', not a fill out the form and bonk on the button type of 'request'. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
