1 |
On Thu, Sep 8, 2011 at 10:03 AM, Thomas Sachau <tommy@g.o> wrote: |
2 |
> Tomáš Chvátal schrieb: |
3 |
>> Start collecting ideas for EAPI5. |
4 |
> |
5 |
> 1) USE-flag based support to cross-compile packages (mostly implemented in multilib-portage) |
6 |
> 2) USE-flag based support to install for different slots (e.g. python, ruby or php) |
7 |
> 3) (internal) USE-flag based support to re-install packages (replacement for |
8 |
> revdep-rebuild/@preserved-rebuild) |
9 |
> |
10 |
> The order of the list is also in the order of how much of it is already implemented and could be |
11 |
> easily drafted. |
12 |
> |
13 |
> The first one already has a working implementation, so might just need some smaller adjustments. |
14 |
> |
15 |
> The second one is already done in some eclasses, afaik php and ruby, but it might be a good idea to |
16 |
> have a general framework for all slotted languages, so there is no need to re-implement the same for |
17 |
> every language. |
18 |
> |
19 |
> The third one is mostly an idea, where packages requiring a rebuild of depending packages define a |
20 |
> specific var (SLOT or some new one line ABI_SLOT, which needs to be updated, when depending packages |
21 |
> need to be rebuild), so that whenever this var is updated, all depending packages have to be |
22 |
> rebuild. This probably needs a bit more of discussion and thinking to get it properly drafted. |
23 |
|
24 |
I thought the usual problem behind this wasn't so much the |
25 |
implementation but instead was getting maintainers to change the |
26 |
ABI_SLOT on a library would be difficult. Either they would do it too |
27 |
often (unnecessarily) or they would not do it enough (so we would |
28 |
still need revdep & friends.) |
29 |
|
30 |
> |
31 |
> |