general-concepts/emerge-and-ebuild/text.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22

<?xml version="1.0" encoding="UTF-8"?>
<devbook self="general-concepts/emerge-and-ebuild/">
<chapter>
<title>Emerge and ebuild relationships</title>

<body>

<figure short="How emerge, ebuild and foo.ebuild interact" link="diagram.png" />

<p>
The <c>emerge</c> program is a high level wrapper for <c>ebuild.sh</c> that handles
dependency tracking, safe installs and uninstalls and so on. <c>emerge</c> calls
<c>ebuild.sh</c> during the build process, which in turn handles the ebuild file
and any eclasses. The <c>${D}</c> to <c>${ROOT}</c> install is handled by <c>emerge</c>.
</p>

<todo>https://dev.gentoo.org/~g2boojum/portage.html</todo>

</body>
</chapter>
</devbook>