| 1 |
On 3/12/20 11:23 AM, Alexis Ballier wrote: |
| 2 |
> On Thu, 2020-03-12 at 09:06 +0100, haubi@g.o wrote: |
| 3 |
>> As this native Win32 support is considered highly experimental still, |
| 4 |
>> I |
| 5 |
>> would like to apply the libtool patches for parity via elibtoolize |
| 6 |
>> only, |
| 7 |
>> without applying them in sys-devel/libtool itself yet. |
| 8 |
>> |
| 9 |
> |
| 10 |
> IIRC you need to do it this way, experimental or not: elibtoolize is |
| 11 |
> needed for packages whose autotools have been generated with an old |
| 12 |
> libtool (ie all of them for now). eautoreconf should call elibtoolize, |
| 13 |
> so, after having this in elt-patches, better focus on upstreaming this |
| 14 |
> in libtool itself so that the need for elibtoolize fades away with |
| 15 |
> time. |
| 16 |
|
| 17 |
Actually, sys-devel/libtool should only apply libtool patches that are |
| 18 |
committed upstream already, to not confuse other distros and/or package |
| 19 |
managers when package maintainers use libtoolize ('make dist') on Gentoo. |
| 20 |
|
| 21 |
> |
| 22 |
> You will probably run into the same issues as in the old days with BSD: |
| 23 |
> not all packages run elibtoolize and you do not have a sane way to |
| 24 |
> force this besides editing ebuilds. |
| 25 |
|
| 26 |
Yeah, we do face this issue in Prefix as well. |
| 27 |
|
| 28 |
/haubi/ |
Archives