| … | |
… | |
| 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-branches.xml,v 1.16 2010/05/14 22:04:32 nightmorph Exp $ --> |
7 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-branches.xml,v 1.17 2011/03/02 09:25:49 nightmorph Exp $ --> |
| 8 | |
8 | |
| 9 | <sections> |
9 | <sections> |
| 10 | |
10 | |
| 11 | <abstract> |
11 | <abstract> |
| 12 | Gentoo provides software separated in several branches, depending on stability |
12 | Gentoo provides software separated in several branches, depending on stability |
| 13 | and architectural support. "Mixing Software Branches" inform you how these |
13 | and architectural support. "Mixing Software Branches" inform you how these |
| 14 | branches can be configured and how you can override this separation |
14 | branches can be configured and how you can override this separation |
| 15 | individually. |
15 | individually. |
| 16 | </abstract> |
16 | </abstract> |
| 17 | |
17 | |
| 18 | <version>1.8</version> |
18 | <version>2</version> |
| 19 | <date>2010-05-14</date> |
19 | <date>2011-03-02</date> |
| 20 | |
20 | |
| 21 | <section> |
21 | <section> |
| 22 | <title>Using One Branch</title> |
22 | <title>Using One Branch</title> |
| 23 | <subsection> |
23 | <subsection> |
| 24 | <title>The Stable Branch</title> |
24 | <title>The Stable Branch</title> |
| … | |
… | |
| 85 | </subsection> |
85 | </subsection> |
| 86 | </section> |
86 | </section> |
| 87 | <section> |
87 | <section> |
| 88 | <title>Mixing Stable with Testing</title> |
88 | <title>Mixing Stable with Testing</title> |
| 89 | <subsection> |
89 | <subsection> |
| 90 | <title>The package.keywords location</title> |
90 | <title>The package.accept_keywords location</title> |
| 91 | <body> |
91 | <body> |
| 92 | |
92 | |
| 93 | <p> |
93 | <p> |
| 94 | You can ask Portage to allow the testing branch for particular packages but use |
94 | You can ask Portage to allow the testing branch for particular packages but use |
| 95 | the stable branch for the rest of the system. To achieve this, add the package |
95 | the stable branch for the rest of the system. To achieve this, add the package |
| 96 | category and name you want to use the testing branch of in |
96 | category and name you want to use the testing branch of in |
| 97 | <path>/etc/portage/package.keywords</path>. You can also create a directory |
97 | <path>/etc/portage/package.accept_keywords</path>. You can also create a |
| 98 | (with the same name) and list the package in the files under that directory. |
98 | directory (with the same name) and list the package in the files under that |
| 99 | For instance, to use the testing branch for <c>gnumeric</c>: |
99 | directory. For instance, to use the testing branch for <c>gnumeric</c>: |
| 100 | </p> |
100 | </p> |
| 101 | |
101 | |
| 102 | <pre caption="/etc/portage/package.keywords setting for gnumeric"> |
102 | <pre caption="/etc/portage/package.accept_keywords setting for gnumeric"> |
| 103 | app-office/gnumeric |
103 | app-office/gnumeric |
| 104 | </pre> |
104 | </pre> |
| 105 | |
105 | |
| 106 | </body> |
106 | </body> |
| 107 | </subsection> |
107 | </subsection> |
| … | |
… | |
| 110 | <body> |
110 | <body> |
| 111 | |
111 | |
| 112 | <p> |
112 | <p> |
| 113 | If you want to use a specific software version from the testing branch but you |
113 | If you want to use a specific software version from the testing branch but you |
| 114 | don't want Portage to use the testing branch for subsequent versions, you can |
114 | don't want Portage to use the testing branch for subsequent versions, you can |
| 115 | add in the version in the <path>package.keywords</path> location. In this case |
115 | add in the version in the <path>package.accept_keywords</path> location. In this |
| 116 | you <e>must</e> use the = operator. You can also enter a version range |
116 | case you <e>must</e> use the = operator. You can also enter a version range |
| 117 | using the <=, <, > or >= operators. |
117 | using the <=, <, > or >= operators. |
| 118 | </p> |
118 | </p> |
| 119 | |
119 | |
| 120 | <p> |
120 | <p> |
| 121 | In any case, if you add version information, you <e>must</e> use an operator. If |
121 | In any case, if you add version information, you <e>must</e> use an operator. If |
Parent Directory
| 
Revision Log
| 
Patch