| 1 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
1 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 2 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
2 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 3 | |
3 | |
| 4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.20 2003/12/17 17:05:59 swift Exp $ --> |
4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-system.xml,v 1.21 2003/12/21 17:01:33 swift Exp $ --> |
| 5 | |
5 | |
| 6 | <sections> |
6 | <sections> |
| 7 | <section> |
7 | <section> |
| 8 | <title>Chrooting</title> |
8 | <title>Chrooting</title> |
| 9 | <subsection> |
9 | <subsection> |
| … | |
… | |
| 101 | <body> |
101 | <body> |
| 102 | |
102 | |
| 103 | <p> |
103 | <p> |
| 104 | If you are <e>not</e> using GRP, you must download a recent Portage snapshot |
104 | If you are <e>not</e> using GRP, you must download a recent Portage snapshot |
| 105 | from the Internet. <c>emerge sync</c> does this for you. GRP-users should skip |
105 | from the Internet. <c>emerge sync</c> does this for you. GRP-users should skip |
| 106 | this and continue with <uri link="#doc_chap1_sect5">Optional: Using Distributed |
106 | this and continue with <uri link="#doc_chap1_sect6">Configuring the USE |
| 107 | Compiling</uri> or <uri link="#doc_chap2">Differences between |
107 | variable</uri>. |
| 108 | Stage1, Stage2 and Stage3</uri>. |
|
|
| 109 | </p> |
108 | </p> |
| 110 | |
109 | |
| 111 | <pre caption="Updating Portage"> |
110 | <pre caption="Updating Portage"> |
| 112 | # <i>emerge sync</i> |
111 | # <i>emerge sync</i> |
| 113 | </pre> |
112 | </pre> |
| … | |
… | |
| 115 | <p> |
114 | <p> |
| 116 | If you are warned that a new Portage version is available and that you should |
115 | If you are warned that a new Portage version is available and that you should |
| 117 | update Portage, you can safely ignore it. Portage will be updated for you later |
116 | update Portage, you can safely ignore it. Portage will be updated for you later |
| 118 | on during the installation. |
117 | on during the installation. |
| 119 | </p> |
118 | </p> |
|
|
119 | |
|
|
120 | </body> |
|
|
121 | </subsection> |
|
|
122 | <subsection> |
|
|
123 | <title>Configuring the USE variable</title> |
|
|
124 | <body> |
|
|
125 | |
|
|
126 | <p> |
|
|
127 | <c>USE</c> is one of the most powerful variables Gentoo provides to its users. |
|
|
128 | Several programs can be compiled with or without optional support for certain |
|
|
129 | items. For instance, some programs can be compiled with gtk-support, or with |
|
|
130 | qt-support. Others can be compiled with or without SSL support. Some programs |
|
|
131 | can even be compiled with framebuffer support (svgalib) instead of X11 support |
|
|
132 | (X-server). |
|
|
133 | </p> |
|
|
134 | |
|
|
135 | <p> |
|
|
136 | Most distributions compile their packages with support for as much as possible, |
|
|
137 | increasing the size of the programs and startup time, not to mention an enormous |
|
|
138 | amount of dependencies. With Gentoo you can define with what options a package |
|
|
139 | should be compiled with. This is where <c>USE</c> comes into play. |
|
|
140 | </p> |
|
|
141 | |
|
|
142 | <p> |
|
|
143 | In the <c>USE</c> variable you define keywords which are mapped onto |
|
|
144 | compile-options. For instance, <e>ssl</e> will compile ssl-support in the |
|
|
145 | programs that support it. <e>-X</e> will remove X-server support (note the minus |
|
|
146 | sign in front). <e>gnome gtk -kde -qt</e> will compile your programs with gnome |
|
|
147 | (and gtk) support, and not with kde (and qt) support, making your system fully |
|
|
148 | tweaked for GNOME. |
|
|
149 | </p> |
|
|
150 | |
|
|
151 | <p> |
|
|
152 | The default <c>USE</c> settings are placed in |
|
|
153 | <path>/etc/make.profile/make.defaults</path>. What you place in |
|
|
154 | <path>/etc/make.conf</path> is calculated against these defaults settings. If |
|
|
155 | you add something to the <c>USE</c> setting, it is added to the default list. If |
|
|
156 | you remove something from the <c>USE</c> setting (by placing a minus sign in |
|
|
157 | front of it) it is removed from the default list (if it was in the default list |
|
|
158 | at all). <e>Never</e> alter anything inside the <path>/etc/make.profile</path> |
|
|
159 | directory; it gets overwritten when you update Portage! |
|
|
160 | </p> |
|
|
161 | |
|
|
162 | <p> |
|
|
163 | A full description on <c>USE</c> can be found in the second part of the Gentoo |
|
|
164 | Handbook, <uri link="?part=2&chap=1">Chapter 1: USE flags</uri>. As an |
|
|
165 | example we show a <c>USE</c> setting for a KDE-based system with DVD, ALSA and |
|
|
166 | CD Recording support: |
|
|
167 | </p> |
|
|
168 | |
|
|
169 | <pre caption="Opening /etc/make.conf"> |
|
|
170 | # <i>nano -w /etc/make.conf</i> |
|
|
171 | </pre> |
|
|
172 | |
|
|
173 | <pre caption="USE setting"> |
|
|
174 | USE="-gtk -gnome qt kde dvd alsa cdr" |
|
|
175 | </pre> |
| 120 | |
176 | |
| 121 | </body> |
177 | </body> |
| 122 | </subsection> |
178 | </subsection> |
| 123 | <subsection> |
179 | <subsection> |
| 124 | <title>Optional: Using Distributed Compiling</title> |
180 | <title>Optional: Using Distributed Compiling</title> |
Parent Directory
| 
Revision Log
| 
Patch