1 |
On 08/31/2012 04:03 PM, Zac Medico wrote: |
2 |
> For those who may not know, chromium-os currently uses a |
3 |
> hard-host-depends ebuild as a workaround for our lack of HDEPEND support |
4 |
> [1]. We could easily add HDEPEND in EAPI 5 if we want, since we already |
5 |
> have a Portage patch attached to bug #317337 [2]. Here is a summary of |
6 |
> what that Portage patch will do: |
7 |
> |
8 |
> In EAPI 5 or later, DEPEND has been divided into two parts: |
9 |
> DEPEND for build-time target dependencies, and HDEPEND for |
10 |
> build-time host dependencies. This division is designed |
11 |
> specifically to minimize difficulty in the process of |
12 |
> adapting ebuilds that were written for earlier EAPIs, |
13 |
> and therefore it also minimizes the adjustments that |
14 |
> ebuild developers will have to make to the thought |
15 |
> processes involved when writing ebuilds from scratch. In |
16 |
> an environment that does not involve cross-compilation, |
17 |
> HDEPEND behaves the same as DEPEND. When an ebuild is |
18 |
> converted from EAPI 4 or earlier to EAPI 5 or later, |
19 |
> in order to support cross-compilation environments, some |
20 |
> dependencies may need to be migrated to HDEPEND. |
21 |
> |
22 |
> For ebuilds that have EAPI 5 or later, the emerge |
23 |
> --root-deps option has no effect since it is made obsolete |
24 |
> by division between DEPEND and HDEPEND. If EAPI 4 or |
25 |
> earlier ebuilds are used in combination with EAPI 5 or |
26 |
> later ebuilds, the --root-deps behavior will still be |
27 |
> applied to the EAPI 4 or earlier ebuilds (there is no |
28 |
> behavior change for ebuilds having older EAPIs). |
29 |
> |
30 |
> [1] |
31 |
> http://www.chromium.org/chromium-os/how-tos-and-troubleshooting/portage-build-faq |
32 |
> [2] https://bugs.gentoo.org/show_bug.cgi?id=317337 |
33 |
|
34 |
I like this. It has my support. |