1 |
On Thu, 25 Jul 2013 09:26:48 -0700 |
2 |
""Paweł Hajdan, Jr."" <phajdan.jr@g.o> wrote: |
3 |
|
4 |
> About one month ago I've filed |
5 |
> <https://bugs.gentoo.org/show_bug.cgi?id=474358> about modernizing |
6 |
> toolchain.eclass by creating new toolchain-r1.eclass and migrating |
7 |
> ebuilds using it to the new eclass. |
8 |
> |
9 |
> Please see attachments and review the code. |
10 |
> |
11 |
> One issue has already been raised, and it's prefix-related changes. I |
12 |
> don't know what to change there, but I'm happy to test suggested changes. |
13 |
> |
14 |
> Then there is a question whether toolchain packages should use EAPI 5, |
15 |
> and I think providing an upgrade path is a good concern. Given |
16 |
> portage/python constraints though, it seems to me it would be fine. If |
17 |
> you think it'd be better, I could use a lower EAPI just in case. |
18 |
> |
19 |
> All feedback is welcome. |
20 |
|
21 |
I meant to work on this last week but got distracted. I have a bunch of |
22 |
build changes testing locally but need to make some cross compilers. |
23 |
|
24 |
I don't think we will be moving to 5 very soon. I have nothing against it but |
25 |
Mike might be a harder sell. I want USE deps so I'm going to do 2 at least, |
26 |
then get the prefix guys on board for 3. |
27 |
|
28 |
Like I said on the bug I don't think we want to do a new eclass (or if we did I |
29 |
would make a toolchain-next for masked versions and backport stuff). |
30 |
|
31 |
|
32 |
-- |
33 |
Ryan Hill psn: dirtyepic_sk |
34 |
gcc-porting/toolchain/wxwidgets @ gentoo.org |
35 |
|
36 |
47C3 6D62 4864 0E49 8E9E 7F92 ED38 BD49 957A 8463 |