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