This page shows how Gentoo Studio is built. Comments and suggestions are welcome.

Note: These may not be the latest versions of these files, as Gentoo Studio is under continuous development. If you are interested, please ask for the latest file versions.

In the beginning, Gentoo Studio was an audio-for-Gentoo howto. Then I started manually creating stage4’s. Then I migrated to Catalyst. Somewhere along the way, NeddySeagoon created a sticky on forums.gentoo.org for Gentoo Studio – thanks, Neddy!

The stage4 tarball is built with Catalyst on a Virtualbox VM. This VM’s build and list of installed packages is identical to the system I intend to be up and running when a user installs Gentoo Studio. Before building/updating the stage4 once a month, the VM is updated and any issues are resolved. New additions to the overlay (/var/lib/GentooStudio) are tested on this VM.

The VM update process:

1. eix-sync
2. emerge -vuDN --with-bdeps=y --backtrack=1000 @system @world (--keep-going is not used; if something fails, it needs to be fixed)
3. Check for kernel update. If so, update kernel, save config and update stage4.spec to use this config. Default config is modified to include:
   1. Full preemption
   2. No framebuffers
   3. ALSA Firewire stack
4. emerge --depclean
5. revdep-rebuild

The Catalyst build process. Spec files are linked in each step:

1. stage3 seed downloaded from gentoo.org
2. stage1.spec edited to use seed
3. catalyst -s latest
4. catalyst -f stage1.spec
5. catalyst -f stage2.spec
6. catalyst -f stage3.spec
7. catalyst -f stage4.spec
8. stage4.spec calls fsscript.sh

Other files:

• /etc/security/limits.conf – Looking into converting this to /etc/security/limits.d files.