Porting

Porting Gentoo to new architectures/platforms/etc...

Introduction
As developers expand Gentoo to new architectures and platforms, they may find there is not any real collection of knowledge which explains all the little details of Portage and moving a platform into the experimental release stage. This document aims to address that. Here we port Gentoo Linux to the SuperH architecture, but the details should be pretty straight forward for other architectures and operating systems.

Getting the system running
This is the hardest step by far (really!). There are two ways to get going. You can start with an existing Linux port out there (Debian, RedHat, some random hobbyist distribution, etc...), or you can cross compile the entire system. The first route is the easiest, so we will only cover that in this guide. Simply boot up the system with the existing port and make sure it has all the important packages installed for development. A quick checklist (with recommended minimum versions):


 * binutils (2.20)
 * gcc     (4.4)
 * glibc   (2.11)
 * python  (2.7)
 * rsync
 * wget
 * tar
 * gzip
 * bzip2
 * bash    (must be 2.05b or newer, ver 3 is best, accessible as )

Converting to Gentoo
Once you have these packages, you can easily install Portage. This script has been written to do the task. Simply download it and run:

todo: move this file to the portage tree and parse the portage ebuild ...

We now need to make a profile for the new architecture. To do so, we first create a local ebuild repository (overlay) with the new profile, then active the both the repository and the profile:

Finally, sync up and we should have our Portage tree!

Preparing a seed for Catalyst
Since none of the ebuilds in Portage know about our new arch, we can cheat with and using  as the reference architecture:

Then we simply emerge the system into a new root and create a seed tarball with the result:

Preparing a Portage snapshot for Catalyst
Now we need to add the KEYWORD to all ebuilds in the system set. To do so, one can use command from  to automatically update the ebuilds and their manifests:

Once the Portage tree has been updated, create a Catalyst snapshot:

Before we can make stages with, we need to teach it something about our new arch. Go into and copy one of the small  modules to. Then edit it to reflect the architecture. Finally edit the file in. You just have to update the  and   variables.

Then try building a stage1 with and the seed.

If everything goes well, you should end up with a stage1 tarball which you can then make a stage2 and a stage3 from.

Alternative
If you don't like the idea of running by hand (i know, it sucks), you can grab this script which will generate the Portage snapshot and stage[123] files for you. Simply edit the settings at the top of the script (see above for proper settings). You will still have to move the seed tarball to the Catalyst dir.

Pushing work into the Portage tree
If we don't want all this work to be for nothing, we have to share it :). Here's what needs to be updated so you don't start committing half broken work (and making other developers very angry).

Create the profiles
Our first profile was just a 'make it work' solution. Now you have to create a much more complete one. After you've committed the profile, update the following files in the subdir:

You should declare the profile status in as   for now (it'll keep people from yelling at you, trust me on this).

Start committing KEYWORDS
At this point, you should be able to start updating ebuilds in the tree with the new KEYWORD.