/[gentoo]/xml/htdocs/doc/en/handbook/hb-portage-diverttree.xml
Gentoo

Diff of /xml/htdocs/doc/en/handbook/hb-portage-diverttree.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.15 Revision 1.16
1<?xml version='1.0' encoding='UTF-8'?> 1<?xml version='1.0' encoding='UTF-8'?>
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-diverttree.xml,v 1.15 2010/07/13 22:00:23 nightmorph Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-diverttree.xml,v 1.16 2012/07/24 12:12:52 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<abstract> 11<abstract>
12"Diverting from the Official Tree" gives you some tips and tricks on how to use 12"Diverting from the Official Tree" gives you some tips and tricks on how to use
13your own Portage tree, how to synchronise only the categories you want, inject 13your own Portage tree, how to synchronise only the categories you want, inject
14packages and more. 14packages and more.
15</abstract> 15</abstract>
16 16
17<version>1.7</version> 17<version>2</version>
18<date>2010-07-13</date> 18<date>2012-07-24</date>
19 19
20<section> 20<section>
21<title>Using a Portage Tree Subset</title> 21<title>Using a Portage Tree Subset</title>
22<subsection> 22<subsection>
23<title>Excluding Packages/Categories</title> 23<title>Excluding Packages/Categories</title>
24<body> 24<body>
25 25
26<p> 26<p>
27You can selectively update certain categories/packages and ignore the other 27You can selectively update certain categories/packages and ignore the other
28categories/packages. We achieve this by having <c>rsync</c> exclude 28categories/packages. We achieve this by having <c>rsync</c> exclude
29categories/packages during the <c>emerge --sync</c> step. 29categories/packages during the <c>emerge --sync</c> step.
30</p> 30</p>
31 31
32<p> 32<p>
33You need to define the name of the file that contains the exclude patterns in 33You need to define the name of the file that contains the exclude patterns in
34the <c>--exclude-from</c> variable in your <path>/etc/make.conf</path>. 34the <c>--exclude-from</c> variable in your <path>/etc/portage/make.conf</path>.
35</p> 35</p>
36 36
37<pre caption="Defining the exclude file in /etc/make.conf"> 37<pre caption="Defining the exclude file in /etc/portage/make.conf">
38PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync_excludes" 38PORTAGE_RSYNC_EXTRA_OPTS="--exclude-from=/etc/portage/rsync_excludes"
39</pre> 39</pre>
40 40
41<pre caption="Excluding all games in /etc/portage/rsync_excludes"> 41<pre caption="Excluding all games in /etc/portage/rsync_excludes">
42games-*/* 42games-*/*
43</pre> 43</pre>
44 44
45<p> 45<p>
46Note however that this may lead to dependency issues since new, allowed packages 46Note however that this may lead to dependency issues since new, allowed packages
47might depend on new but excluded packages. 47might depend on new but excluded packages.
48</p> 48</p>
49 49
50</body> 50</body>
51</subsection> 51</subsection>
52</section> 52</section>
53<section> 53<section>
54<title>Adding Unofficial Ebuilds</title> 54<title>Adding Unofficial Ebuilds</title>
55<subsection> 55<subsection>
56<title>Defining a Portage Overlay Directory</title> 56<title>Defining a Portage Overlay Directory</title>
57<body> 57<body>
58 58
59<p> 59<p>
60You can ask Portage to use ebuilds that are not officially available through the 60You can ask Portage to use ebuilds that are not officially available through the
61Portage tree. Create a new directory (for instance 61Portage tree. Create a new directory (for instance
62<path>/usr/local/portage</path>) in which you store the 3rd-party ebuilds. Use 62<path>/usr/local/portage</path>) in which you store the 3rd-party ebuilds. Use
63the same directory structure as the official Portage tree! 63the same directory structure as the official Portage tree!
64</p> 64</p>
65 65
66<p> 66<p>
67Then define PORTDIR_OVERLAY in <path>/etc/make.conf</path> and have it point to 67Then define PORTDIR_OVERLAY in <path>/etc/portage/make.conf</path> and have it
68the previously defined directory. When you use Portage now, it will take those 68point to the previously defined directory. When you use Portage now, it will
69ebuilds into account as well without removing/overwriting those ebuilds the next 69take those ebuilds into account as well without removing/overwriting those
70time you run <c>emerge --sync</c>. 70ebuilds the next time you run <c>emerge --sync</c>.
71</p> 71</p>
72 72
73</body> 73</body>
74</subsection> 74</subsection>
75<subsection> 75<subsection>
76<title>Working with Several Overlays</title> 76<title>Working with Several Overlays</title>
77<body> 77<body>
78 78
79<p> 79<p>
80For the powerusers who develop on several overlays, test packages before they 80For the powerusers who develop on several overlays, test packages before they
81hit the Portage tree or just want to use unofficial ebuilds from various 81hit the Portage tree or just want to use unofficial ebuilds from various
82sources, the <c>app-portage/layman</c> package brings you 82sources, the <c>app-portage/layman</c> package brings you
83<c>layman</c>, a tool to help you keep the overlay repositories up to date. 83<c>layman</c>, a tool to help you keep the overlay repositories up to date.
84</p> 84</p>
85 85

Legend:
Removed from v.1.15  
changed lines
  Added in v.1.16

  ViewVC Help
Powered by ViewVC 1.1.20