Jump to: navigation, search


7,549 bytes removed, 9 months ago
Update ego upstream location
|description=Metro is the Funtoo Linux automated build system, and is used to build Funtoo Linux stage tarballs.
|source=[ GitHub]}}
{{Subpages|AutoSetup,How Metro WorksManual Setup,Concepts and Terminology,Configuring Metro,Recipes,Automation,Data Model,Recipes}}
== Introduction ==
Metro is the tool used by Funtoo Linux to build new releases of Funtoo Linux. It is also available to the public and can be used to build custom versions of Funtoo Linux, or used by developers to perform build testing. This page documents how to install, configure and use Metro. Also note that there is various additional supplemental documentation available on sub-pages, with links above.
== Installation ==
 <!--T:21-->'''The recommended and supported method''' is to use the Git repository of Metro. === Prerequisites ===
<!--T:24-->Next, clone the master git repository as follows: <!--T:25-->{{console|body=# ##i##cd /root# ##i##git clone git:// ##i##cp /root/metro/metro.conf ~/.metro}} <!--T:26-->You will now have a directory called {{c|/root/metro}} that contains all the Metro source code.=== Setting up ego=Prerequisites for QEMU Support ==Now, we will set the {{c|ego}}, administration tool of Funtoo Linux. The way it is used with metro is independent from {{c|app-admin/ego}} installed on your box. Setup is easy as follows:{{console|body=# ##i##cd /root# ##i##git clone}}This way you will have {{c|/root/ego}} directory with {{c|ego}} binary that is then used by metro. <!--T:28-->Metro is now installed. It's time to customize it for your local system.
You may wish to use the new [[Metro/AutoSetup|autosetup]] script which uses a curses based menu now supports building arm-32bit and allows for quickly setting up and running builds base arm-64bit stages on your choices without requiring any manual stepsx86-64bit systems, using qemu. Please see To enable this functionality, it isnecessary to emerge {{Package|app-emulation/qemu}} with the [[Metro AutoSetup]] page for more detailsfollowing settings.
First, add the following to{{f|/etc/portage/package.use}}:
= Build your own tailored stage3 = <!--T:70--> <!--T:71-->Metro can be easily configured for building custom stage3 by including additional packages. You can find following directory {{c|/etc/builds/packages}} in your copy of metro repository and a corresponding {{c|arch}} configuration files inside:{{file|name=/etc/builds/packagesportage/x86-64bitpackage.confuse|body=[section emerge]app-emulation/qemu static-userdev-libs/glib static-libspackages: [sys-apps/attr static-libs sys-kernellibs/debianzlib static-sourceslibs]dev-libs/libpcre static-libs
Notice a {{c|debian-sources}} ebuild is added for all 64-bit stages. Modify the file to include (or exclude in case Funtoo add additional) packages of your choice. They will be included in your custom stage3 portage's world file.
= Building Gentoo stages = <!--T:98-->
Metro can also build Gentoo stages. After switching to Funtoo profile, see metro require additional steps for this. We have an open bug for this -- it is simply due to the fact that we focus on ensuring Funtoo Linux builds and building Gentoo is a lower priority. Historical note: Funtoo Linux originally started as a fork of Gentoo Linux so that metro could reliably build Gentoo stages.
= Advanced Features = <!--T:100-->
Metro also includes a number of advanced features that can be used to automate builds and set up distributed build servers. These features require you to {{c|emerge sqlalchemy}}, as SQLite is used as a dependency and also {{c|emerge dev-python/lxml}} as this is needed for index file generation.
== Repository Management == <!--TNext, the following should be added to {{f|/etc/make.conf}}:102-->
<!--T:103-->Metro includes a script in the {{c|scripts}} directory called {{c|buildrepo}}. Buildrepo serves as the heart of Metro's advanced repository management features. === Initial Setup === <!--T:104--> <!--T:105-->To use {{c|buildrepo}}, you will first need to create a {{f|.buildbot}} configuration file. Here is the file I use on my AMD Jaguar build server: <!--T:106-->{{file|name=/rootetc/make.buildbot|lang=pythonconf|body=builds QEMU_USER_TARGETS= ( "funtoo-current", "funtoo-current-hardenedaarch64 arm",) <!--T:107-->arches = ( "x86-64bit", "pure64") <!--T:108-->subarches = ( "amd64-jaguar", "amd64-jaguar-pure64",) <!--T:109-->def map_build(build, subarch, full, full_date): # arguments refer to last build... if full == True: buildtype = ( "freshen", ) else: buildtype = ("full", ) # return value can be a string like "full+openvz" or a sequence type like [ "freshen", "openvz" ] return buildtype
<!--T:110-->This file is actually a python source file that defines the tuples {{c|builds}}, {{c|arches}} and {{c|subarches}}. These variables tell {{c|buildrepo}} which builds, arches and subarches it should manage. A {{c|map_build()}} function is also defined which {{c|buildbot}} uses to determine what kind of build to perform. The arguments passed to the function are based on the last successful build. The function can read these arguments and return a string to define the type of the next build. In the above example, the {{c|map_build()}} function will cause the next build after a freshen build to be a full build, and the next build after a full build to be a freshen buildThen, so that the build will alternate between full and freshen. == Automated Builds == <!--Temerge qemu:111-->
Once the {{c|.buildbot}} file has been created, the {{c|buildrepo}} and {{c|}} tools are ready to use. Here's how they work. These tools are designed to keep your repository ({{c|path/mirror}} in {{f|/root/.metro}} up-to-date by inspecting your repository and looking for stages that are out-of-date.
To list the next build that will be performed, do this -- this is from my ARM build server:
# ##i##.emerge app-emulation/buildrepo nextbuildbuild=funtoo-currentarch_desc=arm-32bitsubarch=armv7a_hardfpfulldate=2015-02-08nextdate=2015-02-20failcount=0target=fullextras=''qemu
<!--T:115-->If no output is displayedFrom this point forward, then all your builds are up-to-datesupport for ARM on x86 systems should work transparently. Metro will take care of compiling a wrapper for qemu and temporarily installing the static version of qemu inside the stage chroot so that ARM binaries will run transparently on x86 systems. Metro will also automatically register qemu as a "binary format" with the kernel.
=== Cloning Metro ===<!--T:11624-->To actually run the next build, run '''The recommended and supported method for installing metro''' is to clone metro's git repository to {{cf|}}. Clone the master git repository as follows:
# ##i##cd /root# ##i##git clone ##i##cp /root/metro/metro.conf ~/buildbot.shmetro
<!--T:118-->If you're thinking that {{cTip|buildbotThe {{f|/root/.shmetro}} would file contains the system metro configuration, and defines where the build repository and other files should be a good candidate stored. Defaults are typically fine for a cron jobmost users, you've got and {{f|/home/mirror/funtoo}} will be used as the right idea!build repository path. For more information on configuration settings available, see [[Metro/Configuring Metro]].}}
=== List Builds === <!--T:119-->You will now have a directory called {{c|/root/metro}} that contains all the Metro source code.
<!--T:120-->=== Setting up ego===To get a quick look at our repositoryNow, let's run we will set the {{c|buildrepo failsego}} command: <!, administration tool of Funtoo Linux. The way it is used with metro is independent from {{c|app-admin/ego}} installed on your box. This local cloned copy of ego allows metro to potentially use a newer version of ego than what is already installed on your system, or to function under other non-TFuntoo distributions like Gentoo or Ubuntu. Set up as follows:121-->
# /buildrepo failsroot 0 2015-02-18 # ##i##git clone https:/home/mirror/ 0 2015-02-18 core/home/mirror/funtoo/funtoo-current/pure64/amd64-jaguar-pure64ego.git 0 2015-02-18 /home/mirror/funtoo/funtoo-current-hardened/x86-64bit/amd64-jaguar}} 0 2015-02-18 This way you will have {{c|/homeroot/mirror/funtoo/funtoo-current-hardened/pure64/amd64-jaguar-pure64 ego}} directory with {{c|ego}}binary that is then used by metro.
<!--T:122-->On my AMD Jaguar build server, on Feb 20, 2015, this lists all the builds that {{c|buildrepo}} has been configured to manage. The first number on each line is a '''failcount''', which is the number of consecutive times that the build has failed. A zero value indicates that everything's okay. The failcount is an important feature of the advanced repository management features. Here are a number of behaviors that are implemented based on failcount:== Build Repository Setup ==
<!--T:123-->* If Metro uses a repository to store built stages and snapshots, which typically resides at {{cf|}} tries . There are two methods to set up your build a stage and the build fails, the failcount is incrementedrepository -- it can be done [[Metro/Manual Setup|manually]] or [[Metro/AutoSetup|with our auto-setup script.* If the build succeeds for a particular build, the failcount ]] The auto-setup script is reset to zero.* Builds with the lowest failcount are prioritized by {{buildrepo}} to build nextof course faster and easier, to steer towards builds that are more likely to complete successfully.* Once while the failcount reaches 3 for manual method may give you a particular build, it is removed from deeper understanding of how the build rotationrepository internals work.
==First Build = Resetting Failcount === <!--T:124-->
<!--T:125-->If a Once your build repository has issuesbeen set up, the failcount for you can start your first build using a build will reach 3, at which point it will be pulled out of build rotation. To clear failcount, so that these builds are attempted again -- possibly fixed by new updates command similar to the Portage tree -- use {{c|buildrepo zap}}one below:
# ##i## /root/metro/scripts/buildrepo zapRemoving /mnt/data/funtoo/funtoo-current/arm-32bit/armv7a_hardfp/.control/.failcount...Removing /mnt/data/funtoo/funtoo-current/arm-32bit/armv6j_hardfp/.control/.failcount...Removing /mnt/data/funtoo/funtoo-current/arm-32bit/armv5te/.control/.failcount...}} == Repository Maintenance == <!--T:127--> <!--T:128-->A couple of repository maintenance tools are provided: <!--T:129-->* {{c|buildrepo digestgen}} will generate hash files for the archives in your repository, and clean up stale hashes. * {{c|buildrepo index.xml}} will create an index.xml file at the root of your repository, listing all builds available.* {{c|buildrepo clean}} will output a shell script that will remove old stages. No more than the three most recent stage builds for each build/arch/subarch are kept. == Distributed Repositories == <!--T:130--> <!--T:131-->In many situation, you will have a number of build servers, and each will build a subset of your master repository, and then upload builds to the master repository. This is an area of Metro that is being actively developed. For now, automated upload functionality is not enabled, but is expected to be implemented in the relatively near future. However, it is possible to have your master repository differentiate between subarches that are built locally, and thus should be part of that system's {{c|buildbot}} build rotation, and those that are stored locally and built remotely. These builds should be cleaned when {{c|buildrepo clean}} is run, but should not enter the local build rotation. To set this up, modify {{f|/root/ezbuild.buildbot}} and use the {{c|subarches}} and {{c|all_subarches}} variables: <!--T:132-->{{file|name=/root/sh 1.buildbot|desc=Excerpt of .buildbot config for master repository|body=# subarches we are building locally: <!--T:133-->subarches = ( "pentium4", "athlon-xp", "corei7", "corei7-pure64", "generic_32", "i686", "amd64-k8", "amd64-k8-pure64", "core2_64", "core2_64-pure64", "generic_64", "generic_643-pure64",) # Things we need to clean, even if we may not be building: all_subarches = subarches + ( "atom_32", "atom_64", "atom_64release-pure64", "amd64std x86-k10", "64bit amd64-k10-pure64", "amd64-bulldozer", "amd64-bulldozer-pure64", "amd64-steamroller", "amd64-steamroller-pure64", "amd64-piledriver", "amd64-piledriver-pure64", "amd64-jaguar", "amd64-jaguar-pure64", "intel64-haswell", "intel64-haswell-pure64", "intel64-ivybridge-pure64", "intel64-ivybridge", "armv7a_hardfp", "armv6j_hardfp", "armv5te") }}== Using binary cache ==Metro has built-in feature which allows to use binary packages cache rather then building same list of packages from sources. For example, core packages, such as @system are updated at slower pace and it makes sense to enable binary cache to make stage building blazing fast. However, the real disadvantage with using binary cache could be a core package update that due to internal ABI changes require rebuilding of numerous packages from sources. Good example is {{c|sys-libs/ncurses-5}} to {{c|sys-libs/ncurses-6}} major update. This is the case when you would need to disable binary cache and use regular ebuild installation from sources. To enable binary cache, in your metro git repository copy, edit the {{c|common.conf}} {{file|name=/etc/builds/common.conf|desc=Excerpt of default common.conf|body=[section metro] options:options/stage:target: gentoo}}and set {{c|cache/package}}{{file|name=/etc/builds/common.conf|desc=Excerpt of common.conf with binary cache enabled|body=[section metro] options:options/stage: cache/packagetarget: gentoozen full
During stage build metro will save package cache in {{c|/var/tmp/metro/cache/package-cache}}. With any next builds this binary package cache will be used.

Navigation menu