diff options
Diffstat (limited to 'examples/livecd-stage2_template.spec.txt')
-rw-r--r-- | examples/livecd-stage2_template.spec.txt | 309 |
1 files changed, 309 insertions, 0 deletions
diff --git a/examples/livecd-stage2_template.spec.txt b/examples/livecd-stage2_template.spec.txt new file mode 100644 index 0000000..719639f --- /dev/null +++ b/examples/livecd-stage2_template.spec.txt @@ -0,0 +1,309 @@ +# livecd-stage2 example specfile +# used to build a livecd-stage2 iso image + +# The subarch can be any of the supported catalyst subarches (like athlon-xp). +# Refer to the catalyst reference manual for suppurted subarches. +# http://www.gentoo.org/proj/en/releng/catalyst/reference.xml +# example: +# subarch: athlon-xp +subarch: + +# The version stamp is an identifier for the build. It can be anything you wish# it to be, but it is usually a date. +# example: +# version_stamp: 2005.0 +version_stamp: + +# The target specifies what target we want catalyst to do. For building a CD, +# we continue with livecd-stage2 as the target. +# example: +# target: livecd-stage2 +target: + +# The rel_type defines what kind of build we are doing. This is merely another +# identifier, but it useful for allowing multiple concurrent builds. Usually, +# default will suffice. +# example: +# rel_type: default +rel_type: + +# This is the system profile to be used by catalyst to build this target. It is# specified as a relative path from /usr/portage/profiles. +# example: +# profile: default-linux/x86/2005.0 +profile: + +# This specifies which snapshot to use for building this target. +# example: +# snapshot: 20050324 +snapshot: + +# This specifies where the seed stage comes from for this target, The path is +# relative to $clst_sharedir/builds. The rel_type is also used as a path prefix# for the seed. +# example: +# default/livecd-stage1-x86-2004.3 +source_subpath: + +# These are the hosts used as distcc slaves when distcc is enabled in your +# catalyst.conf. It follows the same syntax as distcc-config --set-hosts and +# is entirely optional. +# example: +# distcc_hosts: 127.0.0.1 192.168.0.1 +distcc_hosts: + +# This is an optional directory containing portage configuration files. It +# follows the same syntax as /etc/portage and should be consistent across all +# targets to minimize problems. +# example: +# portage_confdir: /etc/portage +portage_confdir: + +# The cdfstype is used to determine what sort of CD we should build. This is +# used to set the type of loopback filesystem that we will use on our CD. +# Possible options are as follows: +# squashfs - This gives the best compression, but requires a kernel patch. +# zisofs - This uses in-kernel compression and is supported on all platforms. +# normal - This creates a loop without compression. +# noloop - This copies the files to the CD directly, withuot using a loopback. +# example: +# livecd/cdfstype: squashfs +livecd/cdfstype: + +# The archscript is for architecture-dependent configuration. Not all Gentoo +# architectures use their own archscript. Some share with other architectures +# that are similar. +# example: +# livecd/archscript: /usr/lib/catalyst/livecd/runscript/x86-archscript.sh +livecd/archscript: + +# The runscript is the "brains" of the livecd-stage2 target and is designed to +# be architecturer agnostic. It is best not to change this. +# example: +# livecd/runscript: /usr/lib/catalyst/livecd/runscript/default-runscript.sh +livecd/runscript: + +# The cdtar is essentially the bootloader for the CD. It also holds the main +# configuration for the bootloader. On x86/amd64, it also can include a small +# memory testing application, called memtest86+. +# example: +# livecd/cdtar: /usr/lib/catalyst/livecd/cdtar/isolinux-2.13-memtest86+-cdtar.tar.bz2 +livecd/cdtar: + +# This is the full path and filename to the ISO image that the livecd-stage2 +# target will create. +# example: +# livecd/iso: /tmp/installcd-x86-minimal.iso +livecd/iso: + +# A fsscript is simply a shell script that is copied into the chroot of the CD +# after the kernel(s) and any external modules have been compiled and is +# executed within the chroot. It can contain any commands that are available +# via the packages installed by our stages or by the packages installed during +# the livecd-stage1 build. We do not use one for the official release media, so +# there will not be one listed below. The syntax is simply the full path and +# filename to the shell script that you wish to execute. The script is copied +# into the chroot by catalyst automatically. +# example: +# livecd/fsscript: +livecd/fsscript: + +# The splash type determines the automatic arguments for the bootloader on +# supported architectures. The possible options are gensplash and bootsplash. +# example: +# livecd/splash_type: gensplash +livecd/splash_type: + +# This is where you set the splash theme. This theme must be present in either +# /etc/splash or /etc/bootsplash, depending on your livecd/splash_type, before +# the kernel has completed building during the livecd-stage2 target. +# example: +# livecd/splash_theme: livecd-2005.0 +livecd/splash_theme: + +# This is a set of arguments that get passed to the bootloader for your CD. It +# is used on the x86/amd64 release media to enable keymap selection. +# example: +# livecd/bootargs: dokeymap +livecd/bootargs: + +# This is a set of arguments that will be passed to genkernel for all kernels +# defined in this target. It is useful for passing arguments to genkernel that +# are not otherwise available via the livecd-stage2 spec file. +# example: +# livecd/gk_mainargs: --lvm2 --dmraid +livecd/gk_mainargs: + +# This option allows you to specify your own linuxrc script for genkernel to use# when building your CD. This is not checked for functionality, so it is up to +# you to debug your own script. We do not use one for the official release +# media, so there will not be one listed below. +# example: +# livecd/linuxrc: +livecd/linuxrc: + +# This option controls quite a bit of catalyst internals and sets up several +# defaults. Each type behaves slightly differently and is explained below. +# gentoo-release-minimal - This creates an official minimal InstallCD. +# gentoo-release-universal - This creates an official universal InstallCD. +# gentoo-release-livecd - This creates an official LiveCD environment. +# gentoo-gamecd - This creates an official Gentoo GameCD. +# generic-livecd - This should be used for all non-official media. +# example: +# livecd/type: gentoo-release-minimal +livecd/type: + +# This is for the CD's message of the day. It is not required for official +# release media, as catalyst builds a default motd when the livecd/type is set +# to one of the gentoo-* options. This setting overrides the default motd even +# on official media. Since we do not use this for the official releases, it is +# left blank below. +# example: +# livecd/motd: +livecd/motd: + +# This is for blacklisting modules from being hotplugged that are known to cause +# problems. Putting a module name here will keep it from being auto-loaded, +# even if ti is detected by hotplug. +# example: +# livecd/modblacklist: 8139cp +livecd/modblacklist: + +# This is for adding init scripts to runlevels. The syntax for the init script +# is the script name, followed by a pipe, followed by the runlevel in which you +# want the script to run. It looks like spind|default and is space delimited. +# We do not use this on the official media, as catalyst sets up the runlevels +# correctly for us. Since we do not use this, it is left blank below. +# example: +# livecd/rcadd: +livecd/rcadd: + +# This is for removing init script from runlevels. It is executed after the +# defaults shipped with catalyst, so it is possible to remove the defaults using +# this option. It can follow the same syntax as livcd/rcadd, or you can leave +# the runlevel off to remove the script from any runlevels detected. We do not +# use this on the official media, so it is left blank. +# example: +# livecd/rcdel: +livecd/rcdel: + +# This overlay is dropped onto the CD filesystem and is outside any loop which +# has been configured. This is typically used for adding the documentation, +# distfiles, snapshots, and stages to the official media. These files will not +# be available if docache is enabled, as they are outside the loop. +# example: +# livecd/overlay: /tmp/overlay-minimal +livecd/overlay: + +# This overlay is dropped onto the filesystem within the loop. This can be used +# for such things as updating configuration files or adding anything else you +# would want within your CD filesystem. Files added here are available when +# docache is used. We do not use this on the official media, so we will leave +# it blank below. +# example: +# livecd/root_overlay: +livecd/root_overlay: + +# This is here to enable udev support in both catalyst and genkernel. This +# option requires genkernel >= 3.1.0, and is not needed with genkernel >=3.2.0, +# as udev is the default. +# example: +# livecd/devmanager: udev +livecd/devmanager: + +# This is used by catalyst to copy the specified file to /etc/X11/xinit/xinitrc +# and is used by the livecd/type gentoo-gamecd and generic-livecd. While the +# file will still be copied for any livecd/type, catalyst will only create the +# necessary /etc/startx for those types, so X will not be automatically started. +# This is useful also for setting up X on a CD where you do not wish X to start +# automatically. We do not use this on the release media, so it is left blank. +# example: +# livecd/xinitrc: +livecd/xinitrc: + +# This option is used to create non-root users on your CD. It takes a space +# separated list of user names. These users will be added to the following +# groups: users,wheel,audio,games,cdrom,usb +# If this is specified in your spec file, then the first user is also the user +# used to start X. Since this is not used on the release media, it is blank. +# example: +# livecd/users: +livecd/users: + +# This option sets the volume ID of the CD created. +# example: +# livecd/volid: Gentoo Linux 2005.0 X86 +livecd/volid: + +# This option is only used when creating a GameCD. This specifies the file that +# contains the definitions for GAME_NAME and GAME_EXECUTABLE, which are used by +# the GameCD scripts to set some specific options for the game. This is not +# used on the release media, and is therefore blank. +# example: +# gamecd/conf: +gamecd/conf: + +# This option is used to specify the number of kernels to build and also the +# labels that will be used by the CD bootloader to refer to each kernel image. +# example: +# boot/kernel: gentoo +boot/kernel: + +# This option tells catalyst which kernel sources to merge for this kernel +# label. This can use normal portage atoms to specify a specific version. +# example: +# boot/kernel/gentoo/sources: gentoo-sources +boot/kernel/gentoo/sources: + +# This option is the full path and filename to a kernel .config file that is +# used by genkernel to compile the kernel this label applies to. +# example: +# boot/kernel/gentoo/config: /tmp/2.6.11-smp.config +boot/kernel/gentoo/config: + +# This option sets genkernel parameters on a per-kernel basis and applies only +# to this kernel label. This can be used for building options into only a +# single kernel, where compatibility may be an issue. Since we do not use this +# on the official release media, it is left blank, but it follows the same +# syntax as livecd/gk_mainargs. +# example: +# boot/kernel/gentoo/gk_kernargs: +boot/kernel/gentoo/gk_kernargs: + +# This option sets the USE flags used to build the kernel and also any packages +# which are defined under this kernel label. These USE flags are additive from +# the default USE for the specified profile. +# example: +# boot/kernel/gentoo/use: pcmcia usb -X +boot/kernel/gentoo/use: + +# This option appends an extension to the name of your kernel, as viewed by a +# uname -r/ This also affects any modules built under this kernel label. This +# is useful for having two kernels using the same sources to keep the modules +# from overwriting each other. We do not use this on the official media, so it +# is left blank. +# example: +# boot/kernel/gentoo/extraversion: +boot/kernel/gentoo/extraversion: + +# This option is for merging kernel-dependent packages and external modules that +# are configured against this kernel label. +# example: +# boot/kernel/gentoo/packages: pcmcia-cs speedtouch slmodem globespan-adsl hostap-driver hostap-utils ipw2100 ipw2200 fritzcapi fcdsl cryptsetup +boot/kernel/gentoo/packages: + +# This is a list of packages that will be unmerged after all the kernels have +# been built. There are no checks on these packages, so be careful what you +# add here. They can potentially break your CD. +# example: +# livecd/unmerge: acl attr autoconf automake bin86 binutils libtool m4 bison ld.so make perl patch linux-headers man-pages sash bison flex gettext texinfo ccache distcc addpatches man groff lib-compat miscfiles rsync sysklogd bc lcms libmng genkernel diffutils libperl gnuconfig gcc-config gcc bin86 cpio cronbase ed expat grub lilo help2man libtool gentoo-sources +livecd/unmerge: + +# This option is used to empty the directories listed. It is useful for getting +# rid of files that don't belong to a particular package, or removing files from +# a package that you wish to keep, but won't need the full functionality. +# example: +# livecd/empty: /var/tmp /var/cache /var/db /var/empty /var/lock /var/log /var/run /var/spool /var/state /tmp /usr/portage /usr/share/man /usr/share/info /usr/share/unimaps /usr/include /usr/share/zoneinfo /usr/share/dict /usr/share/doc /usr/share/ss /usr/share/state /usr/share/texinfo /usr/lib/python2.2 /usr/lib/portage /usr/share/gettext /usr/share/i18n /usr/share/rfc /usr/lib/X11/config /usr/lib/X11/etc /usr/lib/X11/doc /usr/src /usr/share/doc /usr/share/man /root/.ccache /etc/cron.daily /etc/cron.hourly /etc/cron.monthly /etc/cron.weekly /etc/logrotate.d /etc/rsync /usr/lib/awk /usr/lib/ccache /usr/lib/gcc-config /usr/lib/nfs /usr/local /usr/diet/include /usr/diet/man /usr/share/consolefonts/partialfonts /usr/share/consoletrans /usr/share/emacs /usr/share/gcc-data /usr/share/genkernel /etc/bootsplash/gentoo /etc/bootsplash/gentoo-highquality /etc/splash/gentoo /etc/splash/emergence /usr/share/gnuconfig /usr/share/lcms /usr/share/locale /etc/skel +livecd/empty: + +# This option tells catalyst to clean specific files from the filesystem and is +# very usefu in cleaning up stray files in /etc left over after livecd/unmerge. +# example: +# livecd/rm: /lib/*.a /usr/lib/*.a /usr/lib/gcc-lib/*/*/libgcj* /etc/dispatch-conf.conf /etc/etc-update.conf /etc/*- /etc/issue* /etc/make.conf /etc/man.conf /etc/*.old /root/.viminfo /usr/sbin/bootsplash* /usr/sbin/fb* /usr/sbin/fsck.cramfs /usr/sbin/fsck.minix /usr/sbin/mkfs.minix /usr/sbin/mkfs.bfs /usr/sbin/mkfs.cramfs /lib/security/pam_access.so /lib/security/pam_chroot.so /lib/security/pam_debug.so /lib/security/pam_ftp.so /lib/security/pam_issue.so /lib/security/pam_mail.so /lib/security/pam_motd.so /lib/security/pam_mkhomedir.so /lib/security/pam_postgresok.so /lib/security/pam_rhosts_auth.so /lib/security/pam_userdb.so /usr/share/consolefonts/1* /usr/share/consolefonts/7* /usr/share/consolefonts/8* /usr/share/consolefonts/9* /usr/share/consolefonts/A* /usr/share/consolefonts/C* /usr/share/consolefonts/E* /usr/share/consolefonts/G* /usr/share/consolefonts/L* /usr/share/consolefonts/M* /usr/share/consolefonts/R* /usr/share/consolefonts/a* /usr/share/consolefonts/c* /usr/share/consolefonts/dr* /usr/share/consolefonts/g* /usr/share/consolefonts/i* /usr/share/consolefonts/k* /usr/share/consolefonts/l* /usr/share/consolefonts/r* /usr/share/consolefonts/s* /usr/share/consolefonts/t* /usr/share/consolefonts/v* /etc/splash/livecd-2005.0/16* /etc/splash/livecd-2005.0/12* /etc/splash/livecd-2005.0/6* /etc/splash/livecd-2005.0/8* /etc/splash/livecd-2005.0/images/silent-16* /etc/splash/livecd-2005.0/images/silent-12* /etc/splash/livecd-2005.0/images/silent-6* /etc/splash/livecd-2005.0/images/silent-8* /etc/splash/livecd-2005.0/images/verbose-16* /etc/splash/livecd-2005.0/images/verbose-12* /etc/splash/livecd-2005.0/images/verbose-6* /etc/splash/livecd-2005.0/images/verbose-8* /etc/make.conf.example /etc/make.globals /etc/resolv.conf +livecd/rm: |