| … | |
… | |
| 2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
2 | <!DOCTYPE sections SYSTEM "/dtd/book.dtd"> |
| 3 | |
3 | |
| 4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
4 | <!-- The content of this document is licensed under the CC-BY-SA license --> |
| 5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/1.0 --> |
| 6 | |
6 | |
| 7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.26 2004/12/28 20:01:06 cam Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-use.xml,v 1.27 2005/01/22 01:24:31 cam Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <version>1.23</version> |
11 | <version>1.24</version> |
| 12 | <date>2004-12-28</date> |
12 | <date>2005-01-22</date> |
| 13 | |
13 | |
| 14 | <section> |
14 | <section> |
| 15 | <title>What are USE-flags?</title> |
15 | <title>What are USE-flags?</title> |
| 16 | <subsection> |
16 | <subsection> |
| 17 | <title>The ideas behind USE-flags</title> |
17 | <title>The ideas behind USE-flags</title> |
| … | |
… | |
| 272 | User-defined USE setting as environment variable |
272 | User-defined USE setting as environment variable |
| 273 | </li> |
273 | </li> |
| 274 | </ol> |
274 | </ol> |
| 275 | |
275 | |
| 276 | <p> |
276 | <p> |
| 277 | To view the final <c>USE</c> setting as seen by Portage, run <c>emerge info</c>. |
277 | To view the final <c>USE</c> setting as seen by Portage, run <c>emerge |
| 278 | This will list all relevant variables (including the <c>USE</c> variable) with |
278 | --info</c>. This will list all relevant variables (including the <c>USE</c> |
| 279 | the content used by Portage. |
279 | variable) with the content used by Portage. |
| 280 | </p> |
280 | </p> |
| 281 | |
281 | |
| 282 | <pre caption="Running emerge info"> |
282 | <pre caption="Running emerge --info"> |
| 283 | # <i>emerge info</i> |
283 | # <i>emerge --info</i> |
| 284 | </pre> |
284 | </pre> |
| 285 | |
285 | |
| 286 | </body> |
286 | </body> |
| 287 | </subsection> |
287 | </subsection> |
| 288 | <subsection> |
288 | <subsection> |
| … | |
… | |
| 303 | were emerged on your "old" system but that have been obsoleted by the new USE |
303 | were emerged on your "old" system but that have been obsoleted by the new USE |
| 304 | flags. |
304 | flags. |
| 305 | </p> |
305 | </p> |
| 306 | |
306 | |
| 307 | <warn> |
307 | <warn> |
| 308 | Running <c>emerge depclean</c> is a dangerous operation and should be handled |
308 | Running <c>emerge --depclean</c> is a dangerous operation and should be handled |
| 309 | with care. Double-check the provided list of "obsoleted" packages to make sure |
309 | with care. Double-check the provided list of "obsoleted" packages to make sure |
| 310 | it doesn't remove packages you need. In the following example we add the |
310 | it doesn't remove packages you need. In the following example we add the |
| 311 | <c>-p</c> switch to have depclean only list the packages without removing them. |
311 | <c>-p</c> switch to have depclean only list the packages without removing them. |
| 312 | </warn> |
312 | </warn> |
| 313 | |
313 | |
| 314 | <pre caption="Removing obsoleted packages"> |
314 | <pre caption="Removing obsoleted packages"> |
| 315 | # <i>emerge -p depclean</i> |
315 | # <i>emerge -p --depclean</i> |
| 316 | </pre> |
316 | </pre> |
| 317 | |
317 | |
| 318 | <p> |
318 | <p> |
| 319 | When depclean has finished, run <c>revdep-rebuild</c> to rebuild the |
319 | When depclean has finished, run <c>revdep-rebuild</c> to rebuild the |
| 320 | applications that are dynamically linked against shared objects provided by |
320 | applications that are dynamically linked against shared objects provided by |
Parent Directory
| 
Revision Log
| 
Patch