Build system requirements
Jump to navigation
Jump to search
- we need to be able to layer our distribution on top of F7 (and, later on, F8) [cscott,bernie]
- easy way to resynch with upstream for the packages we need to fork [cscott, bernie]
- stable builds: we all agree we want builds done in a well specified, controlled environment so bugs are reproducible [bernie, cscott, marcopg, dcbw]
- ability to fork and unfork packages for the OLPC distribution [cscott, bernie]
- ability to add/remove custom packages from the build without going through a lengthy review process [bernie]
- ability for some of us to add/remove package ACLs for our developers without going through Fedora admins. [bernie, cscott]
- ability to create short-lived dist tags for experimental or integration streams such as "olpc-xtest", "olpc-sugar", "olpc-trial4", and so on [bernie]
- ability to create new long-lived dist tags for stable builds (say, every 3mo) [cscott]
- maybe some commitment that the Fedora build cluster will be somewhat more available and better performing than in the past. Very frequently our work-flow has been slowed down by builds of trivial packages that would take take more than one hour to complete. [bernie]
- there may be security concerns with building our binaries off-site. I'm sure RH already has strong security measures in place, but as you may know, OLPC has some very special needs. [jg, bernie]
- short-term, we need decent human-readable build changelogs (i.e. describing what was pushed into the build and why.) [mstone, cjb, cscott]