From: John P. Davis Date: Tue, 15 Jun 2004 05:37:27 +0000 (+0000) Subject: adding new examples X-Git-Tag: CATALYST_2_0_6_916~977 X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=c50403b5433124e7abd3642026a386e1fe68354d;p=catalyst.git adding new examples git-svn-id: svn+ssh://svn.gentoo.org/var/svnroot/catalyst/trunk@396 d1e1f19c-881f-0410-ab34-b69fee027534 --- diff --git a/examples/generic_stage_template.spec b/examples/generic_stage_template.spec new file mode 100644 index 00000000..fd70f027 --- /dev/null +++ b/examples/generic_stage_template.spec @@ -0,0 +1,42 @@ +## generic installation stage specfile +## used to build a stage1, stage2, or stage3 installation tarball + +## John Davis + +# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer +# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches. +# example: +# subarch: athlon-xp +subarch: + +# version stamp is an identifier for the build. can be anything you want it to be, but it +# is usually a date. +# example: +# version_stamp: 2004.2 +version_stamp: + +# target specifies what type of build Catalyst is to do. check the catalyst reference manual +# for supported targets. +# example: +# target: stage2 +target: + +# rel_type defines what kind of build we are doing. usually, default will suffice. +# example: +# rel_type: default +rel_type: + +# system profile used to build the media +# example: +# profile: default-x86-2004.0 +profile: + +# which snapshot to use +# example: +# snapshot: 20040614 +snapshot: + +# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.conf) +# example: +# default/stage3-x86-2004.1 +source_subpath: diff --git a/examples/grp_template.spec b/examples/grp_template.spec new file mode 100644 index 00000000..4674d1c5 --- /dev/null +++ b/examples/grp_template.spec @@ -0,0 +1,188 @@ +## generic GRP (Gentoo Reference Platform) specfile +## used to build a GRP set + +## John Davis + +# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer +# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches. +# example: +# subarch: athlon-xp +subarch: + +# version stamp is an identifier for the build. can be anything you want it to be, but it +# is usually a date. +# example: +# version_stamp: 2004.2 +version_stamp: + +# target specifies what type of build Catalyst is to do. check the catalyst reference manual +# for supported targets. +# example: +# target: grp +target: grp + +# rel_type defines what kind of build we are doing. usually, default will suffice. +# example: +# rel_type: default +rel_type: + +# system profile used to build the media +# example: +# profile: default-x86-2004.0 +profile: + +# which snapshot to use +# example: +# snapshot: 20040614 +snapshot: + +# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.conf) +# example: +# default/stage3-x86-2004.1 + +# directories to organize the GRP into +grp: src cd2 + +# use variables to use when building the GRP set +grp/use: + gtk2 + gnome + kde + qt + bonobo + cdr + esd + gtkhtml + mozilla + mysql + perl + ruby + tcltk + acl + cups + ldap + ssl + tcpd + -svga + +# okay, two things here. first, we know we are building stuff to go into the "src" directory +# because of the grp/src line (first part before the / is the build type, second part is +# directory specified in the grp: key). It is identified as a "srcset" which means that these +# packages will be *fetched only* and not compiled. +grp/src/type: srcset +grp/src/packages: + gentoo-sources + gentoo-dev-sources + vanilla-sources + development-sources + iptables + gpm + rp-pppoe + ppp + speedtouch + pciutils + hdparm + hotplug + aumix + xfree + iputils + vixie-cron + sysklogd + metalog + syslog-ng + raidtools + jfsutils + xfsprogs + reiserfsprogs + lvm-user + dosfstools + lilo + grub + superadduser + gentoolkit + chkrootkit + minicom + lynx + rpm2targz + parted + rdate + whois + tcpdump + cvs + unzip + zip + netcat + isdn4k-utils + nforce-net + nforce-audio + iproute + nvidia-kernel + nvidia-glx + ati-drivers + e100 + e1000 + wireless-tools + pcmcia-cs + emu10k1 + evms + linux-wlan-ng + sys-apps/eject + genkernel + +# same as above, but this time we have a "pkgset". this means that we will fetch and compile +# the desired package +grp/cd2/type: pkgset +grp/cd2/packages: + pciutils + hdparm + hotplug + aumix + xfree + dante + tsocks + chkrootkit + minicom + lynx + rpm2targz + parted + rdate + whois + tcpdump + cvs + unzip + zip + netcat + partimage + DirectFB + apache + app-cdr/cdrtools + gnome + evolution + cups + dev-db/mysql + dev-lang/ruby + emacs + enlightenment + fluxbox + kde + libsdl + mozilla + xfce4 + openbox + openoffice + sylpheed + vim + xemacs + xmms + mozilla-firefox + abiword + gaim + tetex + xcdroast + samba + nmap + gradm + ettercap + xchat + dante + tsocks diff --git a/examples/livecd-stage1_template.spec b/examples/livecd-stage1_template.spec new file mode 100644 index 00000000..95e0ca3e --- /dev/null +++ b/examples/livecd-stage1_template.spec @@ -0,0 +1,111 @@ +## livecd-stage1 example specfile +## used to build a livecd-stage1 + +## John Davis + +# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer +# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches. +# example: +# subarch: athlon-xp +subarch: + +# version stamp is an identifier for the build. can be anything you want it to be, but it +# is usually a date. +# example: +# version_stamp: 2004.2 +version_stamp: + +# target specifies what type of build Catalyst is to do. check the catalyst reference manual +# for supported targets. +# example: +# target: stage2 +target: livecd-stage1 + +# rel_type defines what kind of build we are doing. usually, default will suffice. +# example: +# rel_type: default +rel_type: + +# system profile used to build the media +# example: +# profile: default-x86-2004.0 +profile: + +# which snapshot to use +# example: +# snapshot: 20040614 +snapshot: + +# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.conf) +# example: +# default/stage3-x86-2004.1 +source_subpath: + +# use variables that we would like to use when building the LiveCD packages +livecd/use: + -X + -gtk + -svga + ipv6 + socks5 + livecd + fbcon + +# list of packages to be merged into the LiveCD fs. +livecd/packages: + baselayout + livecd-tools + genkernel + ucl + kudzu + module-init-tools + hotplug + irssi + aumix + metalog + pciutils + parted + mt-st + links + star + strace + raidtools + nfs-utils + jfsutils + usbutils + speedtouch + xfsprogs + xfsdump + e2fsprogs + reiserfsprogs + hdparm + nano + less + openssh + dhcpcd + mingetty + pwgen + popt + dialog + rp-pppoe + gpm + screen + mirrorselect + penggy + iputils + hwdata-knoppix + hwsetup + bootsplash + device-mapper + lvm2 + evms + vim + gpart + pwgen + pptpclient + mdadm + tcptraceroute + netcat + ethtool + wireless-tools + ufed diff --git a/examples/livecd-stage2_template.spec b/examples/livecd-stage2_template.spec new file mode 100644 index 00000000..b70c575f --- /dev/null +++ b/examples/livecd-stage2_template.spec @@ -0,0 +1,175 @@ +## livecd-stage2 example specfile +## used to build a livecd-stage2 iso image + +## John Davis + +# subarch can be any of the supported Catalyst subarches (like athlon-xp). Refer +# to the catalyst reference manual (http://www.gentoo.org/proj/en/releng/catalyst) for supported arches. +# example: +# subarch: athlon-xp +subarch: + +# version stamp is an identifier for the build. can be anything you want it to be, but it +# is usually a date. +# example: +# version_stamp: 2004.2 +version_stamp: + +# target specifies what type of build Catalyst is to do. check the catalyst reference manual +# for supported targets. +# example: +# target: stage2 +target: livecd-stage2 + +# rel_type defines what kind of build we are doing. usually, default will suffice. +# example: +# rel_type: default +rel_type: + +# system profile used to build the media +# example: +# profile: default-x86-2004.0 +profile: + +# which snapshot to use +# example: +# snapshot: 20040614 +snapshot: + +# where the seed stage comes from, path is relative to $clst_sharedir (catalyst.conf) +# example: +# default/stage3-x86-2004.1 +source_subpath: + +# which cdfs to use. valid values are zisofs, squashfs, cloop, gcloop, and none +livecd/cdfstype: zisofs + +# archscript and runscript to use. DO NOT CHANGE THESE UNLESS YOU KNOW WHAT YOU ARE DOING. +livecd/archscript: /usr/lib/catalyst/livecd/runscript/x86-archscript.sh +livecd/runscript: /usr/lib/catalyst/livecd/runscript/default-runscript.sh + +# bootloader for the LiveCD - DO NOT CHANGE UNLESS YOU KNOW WHAT YOU ARE DOING. +livecd/cdtar: /usr/lib/catalyst/livecd/cdtar/isolinux-2.08-memtest86-cdtar.tar.bz2 + +# (optional) create a iso and place it in the location specified +# livecd/iso: /tmp/gentoo.iso + +# (optional) run this script in the LiveCD chroot to tweak the LiveCD fs +# livecd/fsscript: /tmp/myscript.sh + +# (optional) files to be added to the final livecd product. note that they *are not* in the loopback +# fs itself, but in /mnt/cdrom when the cd is booted. +# livecd/overlay: /tmp/files_for_livecd + +# "global" arguments that are to be passed to genkernel +#livecd/gk_mainargs: --makeopts=-j3 + +# tweaks things such as the MOTD for release LiveCDs +#livecd/type: gentoo-release-universal + +# the standard Gentoo release MOTD is included with Catalyst +#livecd/motd: /usr/lib/catalyst/livecd/files/motd.txt + +# Put directories, files (README,Handbook), etc that you want to show up in /mnt/cdrom +# when the LiveCD is booted in the overlay. The layout that is in the overlay +# mirrors how it will be on the LiveCD. +#livecd/overlay: /tmp/livecd-overlay + +# list of modules that you want to blacklist for hotplug +#livecd/modblacklist: siimage eth1394 + +# bootsplash theme to use - must be present in /etc/bootsplash of the +# livecd-stage1. +#livecd/bootsplash: livecd-2004.1 + +# let catalyst know how many kernels to build, and what their names are +boot/kernel: gentoo smp + +# for the first kernel (gentoo), let catalyst know what sources to use and what kernel config to use +boot/kernel/gentoo/sources: sys-kernel/gentoo-sources +boot/kernel/gentoo/config: + +# per-kernel arguments for genkernel +#boot/kernel/gentoo/gk_kernargs: --makeopts=-j2 + +# same as the gentoo kernel above, just different data +boot/kernel/smp/sources: sys-kernel/gentoo-dev-sources +boot/kernel/smp/config: + +# per-kernel arguments for genkernel +#boot/kernel/smp/gk_kernargs: --makeopts=-j1 + +#this next line sets any USE settings you want exported to the environment for +#your kernel build *and* during the build of any kernel-dependent packages +boot/kernel/gentoo/use: pcmcia usb +boot/kernel/smp/use: pcmcia usb + +#use this next option to add an extension to the name of your kernel. This +#allows you to have 2 identical kernels on the livecd built with different +#options, and each with their own modules dir in /lib/modules (otherwise +#the second kernel would overwrite the first modules directory. +boot/kernel/gentoo/extraversion: livecd +boot/kernel/smp/extraversion: livecd + +#this next line is for merging kernel-dependent packages after your kernel +#is built. This is where you merge third-party ebuilds that contain kernel +#modules. +boot/kernel/gentoo/packages: + pcmcia-cs + slmodem + linux-wlan-ng + iptables + hostap-driver + ipw2100 + +boot/kernel/smp/packages: + pcmcia-cs + iptables + hostap-driver + ipw2100 + +# remove gcc from the list if you want distcc +livecd/unmerge: + autoconf automake gcc bin86 binutils libtool m4 bison ld.so make perl patch linux-headers man-pages + sash bison flex gettext texinfo ccache addpatches man groff lib-compat python miscfiles +livecd/empty: + /var/tmp + /var/cache + /var/db + /var/empty + /var/cache + /var/lock + /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/X11R6/man + /usr/X11R6/include + /usr/X11R6/lib/X11/config + /usr/X11R6/lib/X11/etc + /usr/X11R6/lib/X11/doc + /usr/src + /usr/share/doc + /usr/share/man + /root/.ccache +livecd/rm: + /lib/*.a + /usr/lib/*.a + /usr/lib/gcc-lib/*/*/libgcj* + /usr/X11R6/lib/*.a + /var/log/emerge.log + /var/log/genkernel.log + diff --git a/examples/snapshot_template.spec b/examples/snapshot_template.spec new file mode 100644 index 00000000..80c93dae --- /dev/null +++ b/examples/snapshot_template.spec @@ -0,0 +1,17 @@ +## portage snapshot example specfile + +## John Davis + +# lets catalyst know what it is building +target: snaphost + +# marks the tarball and makes it unique. Usually, this is a date. +# example: +# version_stamp: 20040611 +version_stamp: + +# portdir_overlay (optional) specifies the path to a portage overlay for inclusion +# in the portage snapshot +# example: +# portdir_overlay: /usr/local/portdir_overlay +portdir_overlay: