On 4:30:26 am 2005-02-09 Torsten Veller <[EMAIL PROTECTED]> wrote: > > What's the use of EXTRA_ECONF and EXTRA_EINSTALL? > > > Right now, users can > - replace the defaults: > prefix, host, mandir, infodir, datadir, sysconfdir, localstatedir > and datadir, infodir, localstatedir, mandir, sysconfir > - add: > anything that doesn't collide with additional arguments in the > ebuild. > So additional arguments in the ebuild have a higher priority then > those in EXTRA_E*. > > Is it the way it should be or should this be change? > Bug #38618 is about this. > > > After this is clarified; there are ebuild not using econf() but > calling configure directly. Wouldn't it be correct to add EXTRA_ECONF > to configure (at the right point)?
I'm not sure how I feel about this particular idea. A lot of the ebuilds that use ./configure directly can't handle econf for one reason or another. Forcing them to respect EXTRA_* is probably not going to have great results. On the other hand, if we just suggest that packagers try to respect it, then it's probably okay in some situations. --Iggy -- [email protected] mailing list
