Revision as of 21:37, 13 February 2011

Metro is the build system for Funtoo stages. It automates the bootstrapping process. This tutorial will take you through setting up and running Metro.

Installing

The now recommended method is to use the Git repository of Metro. First ensure that dev-vcs/git is installed on your system and remove the dev-util/metro package if you had installed it.

# emerge dev-vcs/git

Next, clone the master git repository as follows:

# install -d /root/git
# cd /root/git
# git clone https://github.com/funtoo/metro.git

You will now have a directory called /root/git/metro that contains all the Metro source code. Next, install as follows:

# ln -s /root/git/metro/metro /usr/bin/metro
# ln -s /root/git/metro /usr/lib/metro

Installation complete!

Configuration

/usr/lib/metro/etc/metro.conf is Metro's master configuration file. The [path/mirror] section defines where Metro will look for things it needs and also dump things it creates. As initially configured, Metro is set up to build Funtoo and Gentoo stage tarballs and place them in the /home/mirror/linux directory:

# Mirror Paths - where to find required files and where to put created files

[section path/mirror]

: /home/mirror/linux

If you want to change the location of your mirror on disk, then edit the /home/mirror/linux line (which defines the path/mirror variable) to point to another directory. For the purpose of the following steps, set an environment variable:

# export METRO_MIRROR=/home/mirror/linux

Of course, set the environment variable to whatever location you used in the configuration file.

Metro First Steps

Daniel Robbins maintains Metro, so it comes pre-configured to successfully build both Gentoo and Funtoo releases. The best way to get started with Metro is to mimic the steps used to build a new release of Gentoo or Funtoo. After this is working well for you, you can start looking at customizing, tweaking, and extending things.

Seeds and Build Isolation

At this point, you may be wondering how Metro creates its first stage tarball. As you may have guessed, Metro cannot create a stage tarball out of thin air. To build a new stage tarball, Metro must use an existing, older stage tarball called a "seed" stage. This "seed" stage typically is used as the build environment for creating the stage we want.

Metro can use two kinds of seed stages. Traditionally, Metro has used a stage3 as a seed stage. This stage3 is then used to build a new stage1, which in turn is used to build a new stage2, and then a new stage3. This is generally the most reliable way to build Gentoo or Funtoo, so it's the recommended approach.

Let's quickly review how this might work. Say you wanted to build a new core2_32 stage3 tarball. The recommended method of doing this would be to grab an existing generic pentium4 stage3 tarball to use as your seed stage. We would configure Metro to use this generic pentium4 stage3 to build a new stage1 for the Core_2 32bit. For this process, the generic pentium4 stage3 would provide the build environment for creating our new stage1. Then, the new stage1 would serve as the build environment for creating the new Core_2 32bit stage2. And the new Core_2 32bit stage2 would serve as the build environment for creating the new Core_2 32bit stage3.

A week later, you may want to build a brand new Core_2 32bit stage3 tarball. Rather than starting from the original pentium4 stage3 again, you'd probably configure Metro to use the most-recently-built Core_2 32bit stage3 as the seed. Metro has built-in functionality to make this easy, allowing it to easily find and track the most recent stage3 seed available.

Another important concept to mention here is something called build isolation. Because Metro creates an isolated build environment, and the build environment is explicitly defined using existing, tangible entities -- a seed stage and a portage snapshot -- you will get consistent, repeatable results. In other words, the same seed stage, portage snapshot and build instructions will generate an essentially identical result, even if you perform the build a month later on someone else's workstation.

Trying a Real Build

To get this all started, we need to bootstrap the process by downloading an initial seed stage3 to use for building and place it in is proper location in /home/mirror/linux, so that Metro can find it. We will also need to create some special "control" files in /home/mirror/linux, which will allow Metro to understand how it is supposed to proceed.

Step 1: Set up pentium4 repository (local build)

Assuming we're following the basic steps outlined in the previous section, and building an unstable funtoo (funtoo-current) build for the Intel Core_2 32bit, using a generic pentium4 stage3 as a seed stage, then here the first set of steps we'd perform:

# install -d "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"
# cd "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4"
# install -d 2010-12-24
# cd 2010-12-24
# wget -c http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-32bit/pentium4/2010-12-24/stage3-pentium4-funtoo-current-2010-12-24.tar.xz
# cd ..
# install -d .control/version
# echo "2010-12-24" > .control/version/stage3
# install -d .control/strategy
# echo "local" > .control/strategy/build
# echo "stage3" > .control/strategy/seed

OK, let's review the steps above. First, we create the directory "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4", which is where Metro will expect to find unstable funtoo-current pentium4 builds -- it is configured to look here by default. Then we create a specially-named directory to house our seed x86 stage3. Again, by default, Metro expects the directory to be named this way. We enter this directory, and download our seed x86 stage3 from funtoo.org. Note that the 2010-12-24 version stamp matches. Make sure that your directory name matches the stage3 name too. Everything has been set up to match Metro's default filesystem layout.

Next, we go back to the "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4" directory, and inside it, we create a .control directory. This directory and its subdirectories contain special files that Metro references to determine certain aspects of its behavior. The .control/version/stage3 file is used by Metro to track the most recently-built stage3 for this particular build and subarch. Metro will automatically update this file with a new version stamp after it successfully builds a new stage3. But because Metro didn't actually build this stage3, we need to set up the .control/version/stage3 file manually. This will allow Metro to find our downloaded stage3 when we set up our pentium4 build to use it as a seed. Also note that Metro will create a similar .control/version/stage1 file after it successfully builds an pentium4 funtoo-current stage1.

We also set up .control/strategy/build and .control/strategy/seed files with values of local and stage3 respectively. These files define the building strategy Metro will use when we build pentium4 funtoo-current stages. With a build strategy of local, Metro will source its seed stage from funtoo-current pentium4, the current directory. And with a seed strategy of stage3, Metro will use a stage3 as a seed, and use this seed to build a new stage1, stage2 and stage3.

Step 2: Building the pentium4 stages

Incidentally, if all you wanted to do at this point was to build a new pentium4 funtoo-current stage1/2/3 (plus openvz and vserver templates). You would begin the process by typing:

# /usr/lib/metro/scripts/ezbuild.sh funtoo-current pentium4

If you have a slow machine, it could take several hours to be completed because several "heavy" components like gcc or glibc have to be recompiled in each stage. Once a stage has been successfully completed, it is placed in the "${METRO_MIRROR}/funtoo-current/x32-bit/pentium4/YYYY-MM-DD" subdirectory, where YYYY-MM-DD is today's date at the time the ezbuild.sh script was started or the date you put on the ezscript.sh command line.

Step 3: Set up Core_2 32bit repository (remote build)

In this example, we're going to use this pentium4 funtoo-current stage3 to seed a new Core_2 32bit funtoo-current build. In the Metro terminology this is called a remote build (a stage 3 of a different, but binary compatible, architecture is used as a seed). To get that done, we need to set up the pentium4 build directory as follows:

# cd "${METRO_MIRROR}/funtoo-current/x86-32bit"
# install -d core2_32
# cd core2_32
# install -d .control/strategy
# echo "remote" > .control/strategy/build
# echo "stage3" > .control/strategy/seed
# install -d .control/remote
# echo "funtoo-current" > .control/remote/build
# echo "pentium4" > .control/remote/subarch

The steps we follow are similar to those we performed for the pentium4 directory. However, note the differences. We didn't download a stage, because we are going to use the pentium4 stage to build a new Core_2 32bit stage. We also didn't create the .control/version/stage{1,3} files because Metro will create them for us after it successfully builds a new stage1 and stage3. We are still using a stage3 seed strategy, but we've set the build strategy to remote, which means that we're going to use a seed stage that's not from this particular subdirectory. Where are we going to get it from? The .control/remote directory contains this information, and lets Metro know that it should look for its seed stage3 in the "${METRO_MIRROR}/home/mirror/linux/funtoo-current/x86-32bit/pentium4" directory. Which one will it grab? You guessed it -- the most recently built stage3 (since our seed strategy was set to stage3) that has the version stamp of 2010-12-24, as recorded in "${METRO_MIRROR}/funtoo-current/x86-32bit/pentium4/.control/version/stage3". Now you can see how all those control files come together to direct Metro to do the right thing.

Step 4: Building the Core_2 32bit stages

At this point, you could start building your new Core_2 32bit stage1/2/3 (plus openvz and vserver templates) by typing the following:

# /usr/lib/metro/scripts/ezbuild.sh funtoo-current core2_32

In that case, the produced stages are placed in the "${METRO_MIRROR}/funtoo-current/x32-bit/core2_32/YYYY-MM-DD" subdirectory.

Step 5: The Next Build

At this point, you now have a new Core_2 32bit stage3. If you'd like, you can reconfigure Metro to use the most recently-built Core_2 32bit stage3 as a seed for any new Core_2 32bit builds. To do this, simply type:

# echo "local" > /home/mirror/linux/funtoo-current/x86-32bit/core2_32/.control/strategy/build

Now, Metro will use the most recent Core_2 32bit stage3 as a seed. The .control/remote files you created will be ignored by Metro, since it's no longer going to perform a remote build.