1 |
Zac Medico schrieb: |
2 |
> On 07/01/2012 04:29 AM, Thomas Sachau wrote: |
3 |
>> Matt Turner schrieb: |
4 |
>>> On Fri, Jun 29, 2012 at 10:30 AM, Thomas Sachau <tommy@g.o> wrote: |
5 |
>>>> |
6 |
>>> |
7 |
>>> I'm interested in this because I'm regularly annoyed with the emul- |
8 |
>>> packages and also because multilib is pretty important for mips. |
9 |
>>> |
10 |
>>>> If a package has dependencies, then those dependencies are required to have |
11 |
>>>> at least the same targets enabled as the package |
12 |
>>> |
13 |
>>> That seems like the obvious (but perhaps naive) choice. What about |
14 |
>>> depending on packages that don't install libraries, like x11-proto/ |
15 |
>>> packages or generators like dev-util/indent? |
16 |
>>> |
17 |
>>> Maybe I just don't understand. Would these packages even have ABI flags? |
18 |
>> |
19 |
>> All packages do get the ABI flags (with the needed EAPI or via enabled |
20 |
>> portage feature, which is currently in the multilib branch). |
21 |
>> |
22 |
>> If a package does not install anything ABI-specific (no headers, no libs |
23 |
>> and no binaries), then there is no overhead, since it will just get |
24 |
>> compiled/installed for one ABI, even if multiple ABI flags are enabled. |
25 |
> |
26 |
> For a package like this that does not install anything ABI-specific, |
27 |
> does the package manager still execute phases for each enabled ABI, or |
28 |
> is there some way for the ebuild to indicate whether or not its phases |
29 |
> need to be executed for each enabled ABI? |
30 |
> |
31 |
|
32 |
|
33 |
This is dynamicly checked at runtime, no need to modify the ebuilds and |
34 |
also no needless compilation, when there is no ABI-specific content. |
35 |
|
36 |
A more detailed answer at package manager level: |
37 |
After the src_install phase for the first requested ABI has been |
38 |
finished, the content of $DESTDIR is checked. If there is no ABI |
39 |
specific content, the other enabled ABIs are skipped and the following |
40 |
steps are done as usual. |
41 |
|
42 |
-- |
43 |
|
44 |
Thomas Sachau |
45 |
Gentoo Linux Developer |