On Sun, 25 Sep 2016 11:05:27 +0100 James Le Cuirot <ch...@gentoo.org> wrote:
> I've just started cross-compiling again for the first time in about > two years. Now I remember why I couldn't rely on bashrc for this. > elibtoolize comes from the libtool eclass and you can't inherit > additional eclasses from bashrc. Well, technically you can but it becomes really hackish :) I doubt including elibtoolize in portage/econf/pms is a viable solution: there is way too much code, N patches times M libtool versions to handle, and in rare cases one needs to call elibtoolize with some optional arguments. Specing that would be a pain for no real gain. On the other hand, we could go the complete opposite direction of what has been done in the past years with PMS: provide a generic way to extend ebuild env from profiles, with the ability to "include" some "eclasses", define default phases and pre/post phases hooks. This would have, e.g., saved the need to completely rewrite and spec epatch, avoided every PM to copy/paste default phases implementations from PMS, etc. However, this has somewhat the same disadvantage than eclasses: one commits crap there and breaks every system in subtle ways...
