On Mon, Sep 8, 2008 at 10:44 AM, Alec Warner <[EMAIL PROTECTED]> wrote:
>
> Most obvious failure cases these days have build logs and the build
> logs will specify what the configure command
> was, so the only problematic area is looking at the ebuild to
> determine what will happen during execution. Arguably having
> an ebuildshell would assist here. However, ebuilds are already
> sufficiently complicated by eclass inheritance that reading
> many ebuilds is already difficult and I think this extension does not
> make that significantly worse.
If you're just dealing with the default phases, it's not too hard to
say in advance the exact command that will be executed. Default phases
are well-defined in PMS. So you can look at them to see what will
happend if you define some variable.
For example, for the proposed arguments for src_configure, a
definition would be something like this (taken from Exherbo, just
pretend it says USE instead OPTION and you're done):
default_src_configure()
{
if [[ -x ${ECONF_SOURCE:-.}/configure ]] ; then
econf \
"[EMAIL PROTECTED]" \
$(for s in "${DEFAULT_SRC_CONFIGURE_OPTION_ENABLES}" ; do \
option_enable ${s} ; \
done ) \
$(for s in "${DEFAULT_SRC_CONFIGURE_OPTION_WITHS}" ; do \
option_with ${s} ; \
done )
fi
}
It's quite straightforward.
Regards,
--
Santiago M. Mola
Jabber ID: [EMAIL PROTECTED]
