#4256 NORM Never A: Killjoy, stable builds

[Zarro Boogs per Child]

#4256: Killjoy, stable builds
---------------------+------------------------------------------------------
  Reporter:  marco   |       Owner:  kimquirk      
      Type:  defect  |      Status:  new           
  Priority:  normal  |   Milestone:  Never Assigned
 Component:  distro  |     Version:                
Resolution:          |    Keywords:                
  Verified:  0       |  
---------------------+------------------------------------------------------

Comment(by bernie):

 Replying to [comment:11 bernie]:

 > I agree with marco's requirements and dcbw's solution.

 Sorry if I reply shortly after to argue against myself, but it just
 occurred to me that perhaps it doesn't take that much effort to extend the
 temporary build system done by cscott to do what we desire (i.e.: stable
 binaries).

 If developers were asked to drop source RPMs in their ~/public_srpms,
 directory, what would it take to build them?

 My guess is: just mock and a yum repository with the initial set of RPMs
 needed for the builds. And it won't take anything more than "mock
 foo.src.rpm" to build package foo in a controlled and reproducible
 environment.  Am I overlooking anything important?

 What else does Koji do that we really need?  Clustering?  Psst.  Nice web
 interface?  bah... Remote CLI interface?  maybe.

 The only thing I disliked about the joyride infrastructure was that there
 was no way to trigger a build immediately, so you either had to bug
 cscott, or wait until the next cronjob run to test your jffs2 image.

 This is more of a question than a proposal: do we like to have a
 significant set of Koji feaatures?  Because if we do, there's no point in
 reinventing the wheel, but if we don't Koji is way too much infrastructure
 for what we *really* need.

 As usual, my $0.02, please don't shoot me, etc, etc...

-- 
Ticket URL: <https://dev.laptop.org/ticket/4256#comment:12>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system