| 1 |
About one month ago I've filed |
| 2 |
<https://bugs.gentoo.org/show_bug.cgi?id=474358> about modernizing |
| 3 |
toolchain.eclass by creating new toolchain-r1.eclass and migrating |
| 4 |
ebuilds using it to the new eclass. |
| 5 |
|
| 6 |
Please see attachments and review the code. |
| 7 |
|
| 8 |
One issue has already been raised, and it's prefix-related changes. I |
| 9 |
don't know what to change there, but I'm happy to test suggested changes. |
| 10 |
|
| 11 |
Then there is a question whether toolchain packages should use EAPI 5, |
| 12 |
and I think providing an upgrade path is a good concern. Given |
| 13 |
portage/python constraints though, it seems to me it would be fine. If |
| 14 |
you think it'd be better, I could use a lower EAPI just in case. |
| 15 |
|
| 16 |
All feedback is welcome. |
| 17 |
|
| 18 |
Paweł |
Archives