1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
|
# generic installation stage specfile
# used to build a stage1, stage2, or stage3 installation tarball
# The subarch can be any of the supported catalyst subarches (like athlon-xp).
# Refer to "man catalyst" or <https://wiki.gentoo.org/wiki/Catalyst>
# for supported subarches
# 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: 2006.1
version_stamp:
# The target specifies what target we want catalyst to do. For stages, the
# supported targets are: stage1 stage2 stage3
# example:
# target: 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 /var/db/repos/gentoo/profiles.
# example:
# profile: default-linux/x86/2006.1
profile:
# This specifies which snapshot to use for building this target.
# example:
# snapshot: 2006.1.tar.bz2
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. It must be a complete filename including the extension.
# example:
# default/stage3-x86-2006.1.tar.bz2
source_subpath:
# The prefered compression/decompression command and algorithm to use
# for creating the final stage tarballs. For decompression the configured
# method will be used if the file's extension is one of it's types listed.
# Otherwise it will pick one that does. Of course you must ensure to have
# the correct package installed that supplies that command/algorithm type.
# available options are:
# Name Compressor Extension
# "rsync" : None
# "lbzip2" : tar.bz2
# "bzip2" : tar.bz2
# "tar" : tar
# "xz" : tar.xz
# "pixz" : tar.xz
# "gzip" : tar.gz
# "squashfs" : squashfs, sfs
#
compression_mode: lbzip2
# Optional arch specification which applies only to the squashfs commpression modes
# default is None
compressor_arch":
# Optional compressor options to add to the compression command
# Defaults to a predetermined set of xattribute options
# To disable the defaults uncomment the following line
#compressor_options": None
# Or to specify your own (overrides the defaults)
# uncomment this next line and add your own options.
#compressor_options":
# The search order to use for determining the decompressor
# to use on the source file. i.e. check the extensions it is capable of
# decompressing to find a match. Use the list above for the modes available.
#Note: rsync is a special case, do not include it below.
#
decompressor_search_order: lbzip2 bzip2 tar pixz xz gzip squashfs
# 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:
# This option specifies the location of the ebuild repositories that you would
# like to have used when building this target. It takes a space-separated list
# of directory names.
# example:
# repos: /usr/local/portage
repos:
# This allows the optional directory containing the output packages for
# catalyst. Mainly used as a way for different spec files to access the same
# cache directory. Default behavior is for this location to be autogenerated
# by catalyst based on the spec file.
# example:
# pkgcache_path: /tmp/packages
pkgcache_path:
# These options are only available when building a stage1 or stage2 target and
# are all optional. These allow for emulating the changes possible during ai
# bootstrap. Some possible uses of these would be building embedded stages
# requiring a different CHOST or building a stage2 with NPTL support from a
# stage1 tarball that is built without it.
# If left blank, then the catalyst defaults from arch.py are used.
# This option is used to change the CHOST from what is default in the profile
# to whatever you specify. This is useful for building NPTL, for example.
# example:
# chost: i686-pc-linux-gnu
chost:
# This option allows you to change the default CFLAGS that will be used in
# building this stage. This really should remain generic, as putting
# optimizations flags here will build a stage1 tarball that is no longer
# generic.
# example:
# cflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
cflags:
# This is for setting the CXXFLAGS. Generally, this would be set to the same
# as CFLAGS. In fact, it will mirror CFLAGS by default.
# example:
# cxxflags: -Os -pipe -fomit-frame-pointer -mcpu=i686
cxxflags:
# Setting this option sets LDFLAGS in make.conf in your stage. This would be
# useful for setting up an embedded or hardened system.
# example:
# ldflags: -Wl,-O1 -Wl,-z,now
ldflags:
|
GitWeb