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
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
|
<section id='package-ebuild-eapi-2'>
<title>EAPI 2</title>
<section id='package-ebuild-eapi-2-helpers'>
<title>Helpers</title>
<section id='package-ebuild-eapi-2-helpers-doman'>
<title>doman</title>
<section id='package-ebuild-eapi-2-helpers-doman-language-codes'>
<title>Recognition of Language Codes in File Names</title>
<para>
Language codes in file names are now used for path translation.
</para>
<table><title>Man Page Path Translation</title>
<tgroup cols='2' align='left' >
<colspec colname='source'/>
<colspec colname='destination'/>
<thead>
<row>
<entry>Source</entry>
<entry>Destination</entry>
</row>
</thead>
<tbody>
<row>
<entry>foo.1</entry>
<entry>/usr/share/man/man1/foo.1</entry>
</row>
<row>
<entry>foo.lang.1</entry>
<entry>/usr/share/man/lang/man1/foo.1</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
</section>
</section>
<section id='package-ebuild-eapi-2-metadata'>
<title>Metadata</title>
<section id='package-ebuild-eapi-2-metadata-dependencies'>
<title>Dependencies</title>
<section id='package-ebuild-eapi-2-metadata-dependencies-blocker-atoms'>
<title>Blocker Atoms</title>
<section id='package-ebuild-eapi-2-metadata-dependencies-blocker-atoms-new-meaning'>
<title>New Meaning for Old Syntax</title>
<para>
Blocker atoms which use the previously existing !atom syntax now have
a slightly different meaning. These blocker atoms indicate that
conflicting packages may be temporarily installed simultaneously. When
temporary simultaneous installation of conflicting packages occurs, the
installation of a newer package may overwrite any colliding files that
belong to an older package which is explicitly blocked. When such file
collisions occur, the colliding files cease to belong to the older
package, and they remain installed after the older package is
eventually uninstalled. The older package is uninstalled only after
any newer blocking packages have been merged on top of it.
</para>
</section>
<section id='package-ebuild-eapi-2-metadata-dependencies-blocker-atoms-new-syntax'>
<title>New !!atom Syntax</title>
<para>
A new !!atom syntax is now supported, for use in special cases for which
temporary simultaneous installation of conflicting packages should not be
allowed. If a given package happens to be blocked my a mixture of atoms
consisting of both the !atom and !!atom syntaxes, the !!atom syntax takes
precedence over the !atom syntax.
</para>
</section>
</section>
<section id='package-ebuild-eapi-2-metadata-dependencies-use'>
<title>USE Dependencies</title>
<para>
When used together with SLOT dependencies, USE dependencies
appear on the right hand side of SLOT dependencies.
</para>
<section id='package-ebuild-eapi-2-metadata-dependencies-use-unconditional'>
<title>Unconditional USE Dependencies</title>
<table><title>Syntax Examples</title>
<tgroup cols='2' align='left' >
<colspec colname='example'/>
<colspec colname='meaning'/>
<thead>
<row>
<entry>Example</entry>
<entry>Meaning</entry>
</row>
</thead>
<tbody>
<row>
<entry>foo[bar]</entry>
<entry>foo must have bar enabled</entry>
</row>
<row>
<entry>foo[bar,baz]</entry>
<entry>foo must have both bar and baz enabled</entry>
</row>
<row>
<entry>foo[-bar,baz]</entry>
<entry>foo must have bar disabled and baz enabled</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id='package-ebuild-eapi-2-metadata-dependencies-use-conditional'>
<title>Conditional USE Dependencies</title>
<table><title>Syntax Examples</title>
<tgroup cols='2' align='left' >
<colspec colname='compact'/>
<colspec colname='expanded'/>
<thead>
<row>
<entry>Compact Form</entry>
<entry>Equivalent Expanded Form</entry>
</row>
</thead>
<tbody>
<row>
<entry>foo[bar?]</entry>
<entry>bar? ( foo[bar] ) !bar? ( foo )</entry>
</row>
<row>
<entry>foo[!bar?]</entry>
<entry>bar? ( foo ) !bar? ( foo[-bar] )</entry>
</row>
<row>
<entry>foo[bar=]</entry>
<entry>bar? ( foo[bar] ) !bar? ( foo[-bar] )</entry>
</row>
<row>
<entry>foo[!bar=]</entry>
<entry>bar? ( foo[-bar] ) !bar? ( foo[bar] )</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
</section>
</section>
<section id='package-ebuild-eapi-2-metadata-src-uri'>
<title>SRC_URI</title>
<section id='package-ebuild-eapi-2-metadata-src-uri-output-file-name-customization'>
<title>Customization of Output File Names</title>
<para>
A new syntax is supported which allows customization of the output
file name for a given URI. In order to customize the output file
name, a given URI should be followed by a "->" operator which,
in turn, should be followed by the desired output file name. As
usual, all tokens, including the operator and output file name,
should be separated by whitespace.
</para>
</section>
</section>
</section>
<section id='package-ebuild-eapi-2-phases'>
<title>Phases</title>
<section id='package-ebuild-eapi-2-phases-src-prepare'>
<title>New src_prepare Phase Function</title>
<para>
A new src_prepare function is called after the src_unpack
function, with cwd initially set to $S.
</para>
</section>
<section id='package-ebuild-eapi-2-phases-src-configure'>
<title>New src_configure Phase Function</title>
<para>
The configure portion of the src_compile function has been
split into a separate function which is named src_configure. The
src_configure function is called in-between the src_prepare and
src_compile functions.
</para>
<programlisting>
src_configure() {
if [[ -x ${ECONF_SOURCE:-.}/configure ]] ; then
econf
fi
}
src_compile() {
if [ -f Makefile ] || [ -f GNUmakefile ] || [ -f makefile ] ; then
emake || die "emake failed"
fi
}
</programlisting>
</section>
<section id='package-ebuild-eapi-2-phases-order'>
<title>Execution Order of Phase Functions</title>
<table><title>Execution Order of Phase Functions</title>
<tgroup cols='1' align='left' >
<colspec colname='name'/>
<thead>
<row>
<entry>Phase Function Name</entry>
</row>
</thead>
<tbody>
<row>
<entry>pkg_setup</entry>
</row>
<row>
<entry>src_unpack</entry>
</row>
<row>
<entry>src_prepare</entry>
</row>
<row>
<entry>src_configure</entry>
</row>
<row>
<entry>src_compile</entry>
</row>
<row>
<entry>src_test</entry>
</row>
<row>
<entry>src_install</entry>
</row>
<row>
<entry>pkg_preinst</entry>
</row>
<row>
<entry>pkg_postinst</entry>
</row>
<row>
<entry>pkg_prerm</entry>
</row>
<row>
<entry>pkg_postrm</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id='package-ebuild-eapi-2-phases-default-functions'>
<title>Default Phase Functions</title>
<para>
The default pkg_nofetch and src_* phase functions are now
accessible via a function having a name
that begins with default_ and
ends with the respective phase function name. For example,
a call to a function with the name default_src_compile is
equivalent to a call to the default src_compile
implementation.
</para>
<table><title>Default Phase Functions</title>
<tgroup cols='1' align='left' >
<colspec colname='name'/>
<thead>
<row>
<entry>Function Name</entry>
</row>
</thead>
<tbody>
<row>
<entry>default_pkg_nofetch</entry>
</row>
<row>
<entry>default_src_unpack</entry>
</row>
<row>
<entry>default_src_prepare</entry>
</row>
<row>
<entry>default_src_configure</entry>
</row>
<row>
<entry>default_src_compile</entry>
</row>
<row>
<entry>default_src_test</entry>
</row>
</tbody>
</tgroup>
</table>
</section>
<section id='package-ebuild-eapi-2-phases-default-function-alias'>
<title>Default Phase Function Alias</title>
<para>
A function named "default" is redefined for each phase so that it
will call the default_* function corresponding to the current phase.
For example, a call to the function named "default" during the
src_compile phase is equivalent to a call to the function named
default_src_compile.
</para>
</section>
</section>
</section>
|