Re: [gentoo-dev] The future of eclasses

[Dan Armak <danarmak@gentoo.org>]

On Thursday 07 February 2002 19:43, you wrote:
> The structure of ebuilds being analogous to the ./configure, make, make
> install manual build sequence is a tremendously valuable "feature" for
> gentoo users in my opinion.  Holds to the "form follows function"
> principal and is relatively transparent to a user who wants to tweak an
> ebuild to suit their needs with minimal effort.  I admit that I am an
> unabashed promoter of the KISS principal (one of my daily working
> mantras, along with "check the connections" :)  Is their anyway that
> eclasses could be "hidden" in portage so that the visible ebuilds
> remains simple, i.e at least gives the appearance of being analogous to
> ./configure, make, make install?  As John Stalker stated in another
> post, the ability to understand, or at least think you understand, with
> minimal effort what is happening when you merge a particular ebuild is
> attractive.
Well, the code in the eclasses is the same exact code that wuold go into the 
ebuilds if the eclasses didn't exist. So you can read and understand it.
If you want to actually see it execute, then a) a vrey detailed log is 
generated in $WORKDIR/temp and b) you can change ebuild.sh's shell to bash -x 
and thus get info on every line executed and every action taken. It's quite 
transparent and comfortable once you're used to it.

BTW, you can export ECLASS_DEBUG_OUTPUT="on" before emerging and you'll get 
that same output to your console.

-- 
Dan Armak
Gentoo Linux Developer, Desktop Team (KDE)
Matan, Israel