Lines 282-313
Link Here
|
282 |
different from the standard root environment. The syntax is the same as for |
282 |
different from the standard root environment. The syntax is the same as for |
283 |
any other bash script. |
283 |
any other bash script. |
284 |
.TP |
284 |
.TP |
285 |
.BR use.defaults |
|
|
286 |
Here we DO NOT define the default USE flags, but the so\-called auto\-USE |
287 |
flags. This rather unknown portage feature activates a USE flag if a |
288 |
specific package is installed and the flag was not explicitly |
289 |
deactivated. This file contains the associations between USE flags and |
290 |
packages that trigger the auto\-USE feature. |
291 |
|
292 |
In other words, if we never put "sdl" or "\-sdl" into our USE, but we |
293 |
have media\-libs/libsdl emerged, then portage automagically sticks "sdl" |
294 |
into our USE for us. |
295 |
|
296 |
.I Format: |
297 |
.nf |
298 |
\- comments begin with # |
299 |
\- one USE flag per line with a list of DEPEND atom bases |
300 |
.fi |
301 |
|
302 |
.I Example: |
303 |
.nf |
304 |
# media\-libs/libsdl will activate "sdl" |
305 |
sdl media\-libs/libsdl |
306 |
# activate tcltk only if we have both |
307 |
# dev\-lang/tcl and dev\-lang/tk |
308 |
tcltk dev\-lang/tcl dev\-lang/tk |
309 |
.fi |
310 |
.TP |
311 |
.BR use.force |
285 |
.BR use.force |
312 |
Some USE flags don't make sense to disable under certain conditions. Here we |
286 |
Some USE flags don't make sense to disable under certain conditions. Here we |
313 |
list forced flags. |
287 |
list forced flags. |