Comments on: Why automatically push to rawhide? http://www.jonmasters.org/blog/2010/12/08/why-automatically-push-to-rawhide/ World Organi[sz]ation Of Broken Dreams Thu, 01 Dec 2011 20:35:15 +0000 http://wordpress.org/?v=2.9 hourly 1 By: Casey Dahlin http://www.jonmasters.org/blog/2010/12/08/why-automatically-push-to-rawhide/comment-page-1/#comment-133219 Casey Dahlin Wed, 08 Dec 2010 19:26:26 +0000 http://www.jonmasters.org/blog/?p=921#comment-133219 If you only want to play with the package yourself, you need to do a scratch build. Regular builds are only to build packages intended to go into the distro. Conceptually I think that's enough, but perhaps the UI should encourage scratch builds first and make regular builds seem more like the exception. If you only want to play with the package yourself, you need to do a scratch build. Regular builds are only to build packages intended to go into the distro. Conceptually I think that’s enough, but perhaps the UI should encourage scratch builds first and make regular builds seem more like the exception.

]]> By: Jesse Keating http://www.jonmasters.org/blog/2010/12/08/why-automatically-push-to-rawhide/comment-page-1/#comment-133218 Jesse Keating Wed, 08 Dec 2010 17:42:26 +0000 http://www.jonmasters.org/blog/?p=921#comment-133218 It has been the plan since the start of the AutoQA effort (a few years ago at a FUDCon in Boston) that there would be a layer of AutoQA between a build completing, and a build being tagged for public consumption. If you wish to get this in place sooner, please donate some time to the AutoQA project. It has been the plan since the start of the AutoQA effort (a few years ago at a FUDCon in Boston) that there would be a layer of AutoQA between a build completing, and a build being tagged for public consumption. If you wish to get this in place sooner, please donate some time to the AutoQA project.

]]> By: Chris Tyler http://www.jonmasters.org/blog/2010/12/08/why-automatically-push-to-rawhide/comment-page-1/#comment-133214 Chris Tyler Wed, 08 Dec 2010 13:36:07 +0000 http://www.jonmasters.org/blog/?p=921#comment-133214 That's what --scratch is all about ... or local sanity checks before Koji submission. That’s what –scratch is all about … or local sanity checks before Koji submission.

]]> By: Kevin Kofler http://www.jonmasters.org/blog/2010/12/08/why-automatically-push-to-rawhide/comment-page-1/#comment-133211 Kevin Kofler Wed, 08 Dec 2010 13:10:36 +0000 http://www.jonmasters.org/blog/?p=921#comment-133211 We can't do any actual development that way. You cannot require us to run Rawhide. How can I do development if my development machine does not work? It's already enough of a PITA to have to deal with Bodhi for released distributions, doing it for Rawhide would break Fedora development entirely. We can’t do any actual development that way.

You cannot require us to run Rawhide. How can I do development if my development machine does not work?

It’s already enough of a PITA to have to deal with Bodhi for released distributions, doing it for Rawhide would break Fedora development entirely.

]]> By: bochecha http://www.jonmasters.org/blog/2010/12/08/why-automatically-push-to-rawhide/comment-page-1/#comment-133205 bochecha Wed, 08 Dec 2010 10:17:42 +0000 http://www.jonmasters.org/blog/?p=921#comment-133205 I kind of agree, since I'd love to be able to use Rawhide on a regular basis, which isn't really possible at the moment. However, I think a much bigger problem is when someone builds a package that will land in Rawhide the next day, breaking everything that depends on this package because the maintainer didn't bother rebuilding them all together or ask for a custom tag. I kind of agree, since I’d love to be able to use Rawhide on a regular basis, which isn’t really possible at the moment.

However, I think a much bigger problem is when someone builds a package that will land in Rawhide the next day, breaking everything that depends on this package because the maintainer didn’t bother rebuilding them all together or ask for a custom tag.

]]>