| 1 |
Hi, everyone. |
| 2 |
|
| 3 |
Since the bug about libtool.eclass [1] has not received any attention, I |
| 4 |
hereby declare maintainer timeout and start working on improving |
| 5 |
the eclass. |
| 6 |
|
| 7 |
The main goals are to: |
| 8 |
|
| 9 |
a. stop requiring every single autoconf ebuild to call elibtoolize |
| 10 |
manually (and effectively having half-'broken' repository), |
| 11 |
|
| 12 |
b. stop bundling the large number of patches with the repository, |
| 13 |
|
| 14 |
c. stop using hacks to find those patches. |
| 15 |
|
| 16 |
The planned steps are to: |
| 17 |
|
| 18 |
1. split epunt_cxx out of eutils: |
| 19 |
|
| 20 |
1.1. split the function into new eclass (PATCH already sent), |
| 21 |
|
| 22 |
1.2. explicitly inherit the new eclass in all ebuilds using epunt_cxx, |
| 23 |
|
| 24 |
1.3. remove implicit inherit from eutils, |
| 25 |
|
| 26 |
1.4. move patches to a package and make the new eclass DEPEND on it. |
| 27 |
|
| 28 |
2. move patches to a package and make libtool.eclass DEPEND on it. |
| 29 |
|
| 30 |
3. copy elibtoolize logic to Portage, and make it apply implicitly |
| 31 |
on econf [do we need to apply it elsewhere?]; disable explicit |
| 32 |
libtoolize when Portage supports that. |
| 33 |
|
| 34 |
4. when new Portage goes stable, start killing libtool.eclass. |
| 35 |
|
| 36 |
Any comments? |
| 37 |
|
| 38 |
[1]:https://bugs.gentoo.org/show_bug.cgi?id=566424 |
| 39 |
|
| 40 |
-- |
| 41 |
Best regards, |
| 42 |
Michał Górny |
Archives