| … | |
… | |
| 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/2.5 --> |
5 | <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 6 | |
6 | |
| 7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml,v 1.1 2012/01/15 09:55:35 swift Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-advanced.xml,v 1.2 2012/02/07 19:17:58 swift Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <abstract> |
11 | <abstract> |
| 12 | As times goes by, Portage evolves and matures further and further. Additional |
12 | As times goes by, Portage evolves and matures further and further. Additional |
| 13 | features are continuously being put in - many of these are only of use by more |
13 | features are continuously being put in - many of these are only of use by more |
| 14 | advanced users. This chapter will go into more detail of these specific |
14 | advanced users. This chapter will go into more detail of these specific |
| 15 | features. |
15 | features. |
| 16 | </abstract> |
16 | </abstract> |
| 17 | |
17 | |
| 18 | <version>1</version> |
18 | <version>2</version> |
| 19 | <date>2012-01-15</date> |
19 | <date>2012-02-07</date> |
| 20 | |
20 | |
| 21 | <section> |
21 | <section> |
| 22 | <title>Introduction</title> |
22 | <title>Introduction</title> |
| 23 | <body> |
23 | <body> |
| 24 | |
24 | |
| … | |
… | |
| 119 | <title>Using /etc/portage/bashrc and affiliated files</title> |
119 | <title>Using /etc/portage/bashrc and affiliated files</title> |
| 120 | <body> |
120 | <body> |
| 121 | |
121 | |
| 122 | <p> |
122 | <p> |
| 123 | When Portage works with ebuilds, it uses a bash environment in which it calls |
123 | When Portage works with ebuilds, it uses a bash environment in which it calls |
| 124 | the various build functions (like src_prepare, src_configure, src_postinst, |
124 | the various build functions (like src_prepare, src_configure, pkg_postinst, |
| 125 | etc.). But Portage also allows you to set up a bash environment yourself. |
125 | etc.). But Portage also allows you to set up a bash environment yourself. |
| 126 | </p> |
126 | </p> |
| 127 | |
127 | |
| 128 | <p> |
128 | <p> |
| 129 | The advantage of using your own bash environment is that you can hook in the |
129 | The advantage of using your own bash environment is that you can hook in the |
Parent Directory
| 
Revision Log
| 
Patch