Difference between revisions of "Build Server"
From stoney cloud
| [unchecked revision] | [unchecked revision] |
(→Overview) |
|||
| Line 3: | Line 3: | ||
* Packages, which don't need to be built, for example [http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html Oracle's Java SE Development Kit] (JDK), can be fetched from the [[Mirror Server]]. | * Packages, which don't need to be built, for example [http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html Oracle's Java SE Development Kit] (JDK), can be fetched from the [[Mirror Server]]. | ||
* Software stacks built upon specialized binary packages, require their own chroot environment. If possible, avoid this. | * Software stacks built upon specialized binary packages, require their own chroot environment. If possible, avoid this. | ||
| + | * For reproducibility, Portage and Profiles are frozen with the help of version control system (git in our case). This is only done on the [[Mirror Server]]. | ||
| + | * When building packages in a chroot environment, the portage and overlay versions need to set. | ||
[[Category:Infrastructure]] | [[Category:Infrastructure]] | ||
Revision as of 11:25, 20 August 2014
Overview
- Base chroot environment for the creation of most binary packages which will be copied to the Binary Package Server.
- Packages, which don't need to be built, for example Oracle's Java SE Development Kit (JDK), can be fetched from the Mirror Server.
- Software stacks built upon specialized binary packages, require their own chroot environment. If possible, avoid this.
- For reproducibility, Portage and Profiles are frozen with the help of version control system (git in our case). This is only done on the Mirror Server.
- When building packages in a chroot environment, the portage and overlay versions need to set.
