/[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.6 Revision 1.7
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.0 --> 5<!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
6 6
7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-diverttree.xml,v 1.6 2005/04/11 21:48:42 so Exp $ --> 7<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-portage-diverttree.xml,v 1.7 2005/10/11 03:49:46 swift Exp $ -->
8 8
9<sections> 9<sections>
10 10
11<version>1.2</version> 11<version>1.3</version>
12<date>2005-04-11</date> 12<date>2005-10-11</date>
13 13
14<section> 14<section>
15<title>Using a Portage Tree Subset</title> 15<title>Using a Portage Tree Subset</title>
16<subsection> 16<subsection>
17<title>Excluding Packages/Categories</title> 17<title>Excluding Packages/Categories</title>
18<body> 18<body>
19 19
20<p> 20<p>
21You can selectively update certain categories/packages and ignore the other 21You can selectively update certain categories/packages and ignore the other
22categories/packages. We achieve this by having <c>rsync</c> exclude 22categories/packages. We achieve this by having <c>rsync</c> exclude
23categories/packages during the <c>emerge --sync</c> step. 23categories/packages during the <c>emerge --sync</c> step.
24</p> 24</p>
25 25
26<p> 26<p>
27By default, <c>rsync</c> will check the contents of 27By default, <c>rsync</c> will check the contents of
47You can ask Portage to use ebuilds that are not officially available through the 47You can ask Portage to use ebuilds that are not officially available through the
48Portage tree. Create a new directory (for instance 48Portage tree. Create a new directory (for instance
49<path>/usr/local/portage</path>) in which you store the 3rd-party ebuilds. Use 49<path>/usr/local/portage</path>) in which you store the 3rd-party ebuilds. Use
50the same directory structure as the official Portage tree! 50the same directory structure as the official Portage tree!
51</p> 51</p>
52 52
53<p> 53<p>
54Then define PORTDIR_OVERLAY in <path>/etc/make.conf</path> and have it point to 54Then define PORTDIR_OVERLAY in <path>/etc/make.conf</path> and have it point to
55the previously defined directory. When you use Portage now, it will take those 55the previously defined directory. When you use Portage now, it will take those
56ebuilds into account as well without removing/overwriting those ebuilds the next 56ebuilds into account as well without removing/overwriting those ebuilds the next
57time you run <c>emerge --sync</c>. 57time you run <c>emerge --sync</c>.
58</p> 58</p>
59 59
60</body> 60</body>
61</subsection> 61</subsection>
62<subsection>
63<title>Working with Several Overlays</title>
64<body>
65
66<p>
67For the powerusers who develop on several overlays, test packages before they
68hit the Portage tree or just want to use unofficial ebuilds from various
69sources, the <c>app-portage/gentoolkit-dev</c> package brings you
70<c>gensync</c>, a tool to help you keep the overlay repositories up to date.
71</p>
72
73<p>
74With <c>gensync</c> you can update all the repositories at once, or select just
75a few of them. Each repository should have a <path>.syncsource</path> file in
76the <path>/etc/gensync/</path> configuration directory which contains the
77repository location, name, ID, etc.
78</p>
79
80<p>
81Suppose you have two additional repositories called <c>java</c> (for the
82in-development java ebuilds) and <c>entapps</c> (for the applications developed
83in-house for your enterprise) then you can update those repositories like so:
84</p>
85
86<pre caption="Using gensync to update a few repositories">
87# <i>gensync java entapps</i>
88</pre>
89
90</body>
91</subsection>
62</section> 92</section>
63<section> 93<section>
64<title>Non-Portage Maintained Software</title> 94<title>Non-Portage Maintained Software</title>
65<subsection> 95<subsection>
66<title>Using Portage with Self-Maintained Software</title> 96<title>Using Portage with Self-Maintained Software</title>
67<body> 97<body>
68 98
69<p> 99<p>
70In some cases you want to configure, install and maintain software yourself 100In some cases you want to configure, install and maintain software yourself
71without having Portage automate the process for you, even though Portage 101without having Portage automate the process for you, even though Portage
72can provide the software titles. Known cases are kernel sources and nvidia 102can provide the software titles. Known cases are kernel sources and nvidia
73drivers. You can configure Portage so it knows that a certain package is 103drivers. You can configure Portage so it knows that a certain package is
74manually installed on your system. This process is called <e>injecting</e> and 104manually installed on your system. This process is called <e>injecting</e> and
75supported by Portage through the 105supported by Portage through the
76<path>/etc/portage/profile/package.provided</path> file. 106<path>/etc/portage/profile/package.provided</path> file.

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20