.gitignore: Ignore build directories
This is what we're ignoring:
$ tree
.
|-- builds # compiled and seed stages
| `-- default
| |-- stage1-i686-2013.1.tar.bz2
| ...
| `-- stage3-i686-2013.1.tar.bz2.DIGESTS
|-- iso # compiled ISOs
| |-- swc-x86.iso
| |-- swc-x86.iso.CONTENTS
| `-- swc-x86.iso.DIGESTS
|-- kerncache # cached kernel compilation
| `-- default
| |-- livecd-stage1-i686-2013.1 # empty (no kernel in livecd-stage1)
| |-- livecd-stage2-i686-2013.1 # lots of kernel compilation stuff
| ...
|-- packages # binary packages from per-stage emerges
| `-- default
| |-- livecd-stage1-i686-2013.1 # emerged during livecd-stage1
| ...
| `-- stage3-i686-2013.1 # emerged during stage3
...
|-- snapshot_cache # unpacked portage snapshots
| `--
20130208
|-- snapshots # packed portage snapshots
| |-- portage-
20130208.tar.bz2
| |-- portage-
20130208.tar.bz2.CONTENTS
| `-- portage-
20130208.tar.bz2.DIGESTS
...
`-- tmp # unpacked stage chroots
|-- default
| |-- livecd-stage1-i686-2013.1
| |-- livecd-stage2-i686-2013.1
| |-- stage1-i686-2013.1
| |-- stage2-i686-2013.1
| `-- stage3-i686-2013.1
`-- portage
`-- portage # unpacked portage snapshot
Initial SWC (Gentoo) Linux 2013.1 x86 configuration
This is the catalyst stuff for building a Gentoo live CD ISO for
Software Carpentry students [1]. It's pretty bare-bones at the
moment, since I tried to keep any non-specfile stuff to a minimum. It
also requires a few patches on top of the current catalyst master
(
37540ff):
livecdfs-update.sh: Assign users to per-user groups
livecd-bashrc: Avoid a startx race by restricting to tty1
livecdfs-update.sh: Use `bash --login` to spawn startx
livecdfs-update.sh: Escape ampersands in STARTX sed expression
fixup: env-update
livecdfs-update.sh: Set XSESSION in /etc/env.d/90xsession
chmod +x all sh scripts so they can run from the git checkout
This is not the most elegant patch series, and some of these patches
will probably be squashed/tweaked before inclusion in upstream
catalyst. I'm not even sure if the per-user group patch is a good
idea (but it shouldn't hurt).
My catalyst.conf file looked like:
digests="md5 sha1 sha512 whirlpool"
contents="auto"
distdir="/usr/portage/distfiles"
envscript="/etc/catalyst/catalystrc"
hash_function="crc32"
options="autoresume kerncache pkgcache seedcache snapcache"
portdir="/usr/portage"
sharedir="/home/wking/src/catalyst"
snapshot_cache="/tmp/catalyst/snapshot_cache"
storedir="/tmp/catalyst"
This repository was checked out into $storedir.
The spec files should be fairly stable (modulo snapshot/version
bumps), but you may need to update the Portage configuration as stable
packages evolve and assorted bugs and incompatibilities are fixed
upstream.
[1]: http://lists.software-carpentry.org/pipermail/discuss-software-carpentry.org/2013-March/000210.html