1 |
Matt Turner schrieb: |
2 |
> On Sun, Jul 1, 2012 at 4:52 PM, Thomas Sachau <tommy@g.o> wrote: |
3 |
>> Matt Turner schrieb: |
4 |
>>> I suppose that's just for ease of implementation? Not having to |
5 |
>>> special-case packages that don't install binaries. |
6 |
>> |
7 |
>> I dont follow. Did you think about only having additional ABI flags for |
8 |
>> certain cases? |
9 |
> |
10 |
> Right. It seems to me that not having the ABI flags for packages like |
11 |
> x11-proto/* would make more sense, but may be more work to implement. |
12 |
|
13 |
The problem here is the following: How do you know before the |
14 |
src_install phase, that a package has no ABI-specific content? And even, |
15 |
if you know that, how would you define the dependency part? This would |
16 |
probably become pretty complex, since it also has to support corner cases. |
17 |
|
18 |
> |
19 |
>> Those ABI flags behave the same as other USE flags: When you change |
20 |
>> them, you have to recompile the package including all the content, that |
21 |
>> has been compiled previously. |
22 |
>> If you want the compile for each ABI seperate, then you would have to |
23 |
>> handle them more like SLOTS, but with a new syntax, with a collision |
24 |
>> handler for the common content and how to handle that in the user UI. I |
25 |
>> fear, that this would be way more complicated to implement in a sane |
26 |
>> way, so i dont plan to go that route. |
27 |
> |
28 |
> Ouch. I already think a mechanism for telling the package manager "you |
29 |
> don't need to rebuild this entire package to turn on /this/ USE flag" |
30 |
> is needed. For ABIs, the situation seems much more clear-cut. In fact, |
31 |
> it seems rather important. |
32 |
|
33 |
This would require a good amount of changes. Since my work with |
34 |
multilib-portage started in 2009 and is still not in the PMS, also i |
35 |
tried to keep it simple, i would not even try to guess an ETA for both |
36 |
of your, in my eyes more complex, ideas. ;-) |
37 |
|
38 |
I of course wont prevent you from preparing them and getting them in, |
39 |
they may be nice, especially removing the need to recompile already |
40 |
compiled code. Just dont underestimate the work with it. |
41 |
|
42 |
|
43 |
-- |
44 |
|
45 |
Thomas Sachau |
46 |
Gentoo Linux Developer |