Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-22 Thread Alexis Ballier
On Sat, 18 Mar 2017 19:29:36 + Peter Stuge wrote: > Alexis Ballier wrote: > > > If elibtoolize results in different binaries being produced, then > > > it's done wrong in the first place. AFAIU the primary goal of > > > elibtoolize logic is to fix issues on recent systems with > > > outdated

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-18 Thread Peter Stuge
Alexis Ballier wrote: > > If elibtoolize results in different binaries being produced, then it's > > done wrong in the first place. AFAIU the primary goal of elibtoolize > > logic is to fix issues on recent systems with outdated build systems. > > Which is certainly not something that needs to be d

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-18 Thread Alexis Ballier
On Sat, 18 Mar 2017 11:21:58 +0100 Michał Górny wrote: > On sob, 2017-03-18 at 11:18 +0100, Alexis Ballier wrote: > > On Sat, 18 Mar 2017 07:53:31 +0100 > > Michał Górny wrote: > > > > > 3. copy elibtoolize logic to Portage, and make it apply > > > > > implicitly on econf [do we need to apply

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-18 Thread Michał Górny
On sob, 2017-03-18 at 11:18 +0100, Alexis Ballier wrote: > On Sat, 18 Mar 2017 07:53:31 +0100 > Michał Górny wrote: > > > > 3. copy elibtoolize logic to Portage, and make it apply implicitly > > > > on econf [do we need to apply it elsewhere?]; disable explicit > > > > libtoolize when Portage supp

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-18 Thread Alexis Ballier
On Sat, 18 Mar 2017 07:53:31 +0100 Michał Górny wrote: > > > 3. copy elibtoolize logic to Portage, and make it apply implicitly > > > on econf [do we need to apply it elsewhere?]; disable explicit > > > libtoolize when Portage supports that. > > > > Related to the above point, if you make it pa

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-17 Thread Michał Górny
On pią, 2017-03-17 at 23:38 +, James Le Cuirot wrote: > On Fri, 17 Mar 2017 18:14:12 +0100 > Michał Górny wrote: > > > Hi, everyone. > > > > Since the bug about libtool.eclass [1] has not received any attention, I > > hereby declare maintainer timeout and start working on improving > > the e

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-17 Thread James Le Cuirot
On Fri, 17 Mar 2017 18:14:12 +0100 Michał Górny wrote: > Hi, everyone. > > Since the bug about libtool.eclass [1] has not received any attention, I > hereby declare maintainer timeout and start working on improving > the eclass. > > The main goals are to: > > a. stop requiring every single aut

Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-17 Thread Alexis Ballier
On Fri, 17 Mar 2017 18:14:12 +0100 Michał Górny wrote: > Hi, everyone. > > Since the bug about libtool.eclass [1] has not received any > attention, I hereby declare maintainer timeout and start working on > improving the eclass. > > The main goals are to: > > a. stop requiring every single aut

[gentoo-dev] [RFC] Master plan for fixing elibtoolize

2017-03-17 Thread Michał Górny
Hi, everyone. Since the bug about libtool.eclass [1] has not received any attention, I hereby declare maintainer timeout and start working on improving the eclass. The main goals are to: a. stop requiring every single autoconf ebuild to call elibtoolize manually (and effectively having half-'bro