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

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

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.3 - (show annotations) (download) (as text)
Mon Nov 15 12:47:47 2004 UTC (9 years, 7 months ago) by swift
Branch: MAIN
Changes since 1.2: +1 -1 lines
File MIME type: application/xml
Moving 2004.3 documentation

1 <?xml version='1.0' encoding='UTF-8'?>
2 <!DOCTYPE sections SYSTEM "/dtd/book.dtd">
3
4 <!-- The content of this document is licensed under the CC-BY-SA license -->
5 <!-- See http://creativecommons.org/licenses/by-sa/2.0 -->
6
7 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/hb-portage-diverttree.xml,v 1.6 2004/11/09 13:05:40 swift Exp $ -->
8
9 <sections>
10
11 <version>1.1</version>
12 <date>October 21, 2004</date>
13
14 <section>
15 <title>Using a Portage Tree Subset</title>
16 <subsection>
17 <title>Excluding Packages/Categories</title>
18 <body>
19
20 <p>
21 You can selectively update certain categories/packages and ignore the other
22 categories/packages. We achieve this by having <c>rsync</c> exclude
23 categories/packages during the <c>emerge --sync</c> step.
24 </p>
25
26 <p>
27 By default, <c>rsync</c> will check the contents of
28 <path>/etc/portage/rsync_excludes</path> (if it exists) which contains the
29 categories or packages that you <e>don't</e> want <c>rsync</c> to update.
30 </p>
31
32 <p>
33 Note however that this may lead to dependency issues since new, allowed packages
34 might depend on new but excluded packages.
35 </p>
36
37 </body>
38 </subsection>
39 </section>
40 <section>
41 <title>Adding Unofficial Ebuilds</title>
42 <subsection>
43 <title>Defining a Portage Overlay Directory</title>
44 <body>
45
46 <p>
47 You can ask Portage to use ebuilds that are not officially available through the
48 Portage tree. Create a new directory (for instance
49 <path>/usr/local/portage</path>) in which you store the 3rd-party ebuilds. Use
50 the same directory structure as the official Portage tree!
51 </p>
52
53 <p>
54 Then define PORTDIR_OVERLAY in <path>/etc/make.conf</path> and have it point to
55 the previously defined directory. When you use Portage now, it will take those
56 ebuilds into account as well without removing/overwriting those ebuilds the next
57 time you run <c>emerge --sync</c>.
58 </p>
59
60 </body>
61 </subsection>
62 </section>
63 <section>
64 <title>Non-Portage Maintained Software</title>
65 <subsection>
66 <title>Using Portage with Self-Maintained Software</title>
67 <body>
68
69 <p>
70 In some cases you want to configure, install and maintain software yourself
71 without having Portage automate the process for you, even though Portage
72 can provide the software titles. Known cases are kernel sources and nvidia
73 drivers. You can configure Portage so it knows that a certain package is
74 manually installed on your system. This process is called <e>injecting</e> and
75 supported by Portage through the
76 <path>/etc/portage/profile/package.provided</path> file.
77 </p>
78
79 <p>
80 For instance, if you want to inform Portage about
81 <c>development-sources-2.6.8.1</c> which you've installed manually, add the
82 following line to <path>/etc/portage/profile/package.provided</path>:
83 </p>
84
85 <pre caption="Example line for package.provided">
86 sys-kernel/development-sources-2.6.8.1
87 </pre>
88
89 </body>
90 </subsection>
91 </section>
92 </sections>

  ViewVC Help
Powered by ViewVC 1.1.20