blob: 29d13cae7c2716813cfd5ce91446b5761ee22496 (
plain)
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
|
<faqs>
<faq>
<title>What is ACCEPT_KEYWORDS for?</title>
<maintainers>
<dev>swift</dev>
</maintainers>
<keywords>
<key>ACCEPT_KEYWORDS</key>
<key>make.conf</key>
<key>portage</key>
</keywords>
<solution>
<p>
ACCEPT_KEYWORDS is a variable you can set in /etc/make.conf to tell
Portage to accept all packages that are marked as ~arch (for instance, by
placing "~x86" as its value).
</p>
<p>
Beware though, this means that your entire system will use packages that
haven't been tested thoroughly yet. You should only do this if you know
how to properly fill in bugreports at <uri
link="https://bugs.gentoo.org">bugzilla</uri>.
</p>
<p>
You might want to use package.keywords instead.
</p>
</solution>
</faq>
<faq>
<title>What is ACPI?</title>
<maintainers>
<dev>swift</dev>
</maintainers>
<keywords />
<solution>
<p>
ACPI stands for Advanced Configuration and Power Interface, a power
management specification that allows the operating system to slow down or
even shut down unused components, effectively managing the power
consumption of your system.
</p>
<p>
It is known to cause some troubles on occasion but is generally safe to
use. To disable ACPI temporarily, add "acpi=off" as a boot parameter to
the kernel.
</p>
</solution>
</faq>
<faq>
<title>What is the CFLAGS variable for?</title>
<maintainers>
<dev>swift</dev>
</maintainers>
<keywords>
<key>CFLAGS</key>
<key>make.conf</key>
<key>Portage</key>
</keywords>
<solution>
<p>
The CFLAGS variable contains flags that you want to pass on to your compiler
when it is building C programs. These flags can contain optimizations that
you wish to use. Please use sane settings as overoptimizations have an
average effect. See /etc/make.conf.examples for examples and sane defaults.
</p>
<p>
For more information on the possible flags, see the "Invoking GCC" chapter
of the online GCC documentation at <uri
link="http://gcc.gnu.org">gcc.gnu.org</uri>.
</p>
</solution>
</faq>
<faq>
<title>What is the CONFIG_PROTECT variable for?</title>
<maintainers>
<dev>swift</dev>
</maintainers>
<keywords>
<key>make.conf</key>
<key>Portage</key>
</keywords>
<solution>
<p>
The CONFIG_PROTECT variable is a variable you can define in
/etc/make.conf. It contains a space-delimited list of directories that
will be protected by Portage' configuration file protection.
</p>
<p>
For more information, consult the <uri
link="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2#doc_chap3">Gentoo
Handbook</uri>
</p>
</solution>
</faq>
<faq>
<title>What is the CONFIG_PROTECT_MAKE variable for?</title>
<maintainers>
<dev>swift</dev>
</maintainers>
<keywords>
<key>make.conf</key>
<key>Portage</key>
</keywords>
<solution>
<p>
With the CONFIG_PROTECT_MAKE variable, which you can set in
/etc/make.conf, you can have a space-delimited list of directories which
should not be protected by Portage's configuration file protection but are
currently protected because their parent directories are.
</p>
<p>
For more information, consult the <uri
link="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=2#doc_chap3">Gentoo
Handbook</uri>.
</p>
</solution>
</faq>
</faqs>
|
GitWeb