On Mon, 23 Aug 2010 19:27:22 -0400 Mike Frysinger <[email protected]> wrote:
> then keep it simple and separate:
> escons() {
> debug-print-function ${FUNCNAME} "$...@}"
>
> set -- scons $(scons_clean_makeopts) ${SCONSOPTS}
> ${EXTRA_ESCONS} "$...@}" echo "$...@}" >&2
> "$...@}"
> }
>
> now you dont have to worry about changes between invocations and the
> developer has a clear path -- if they need to force a serial build
> for example, they can either append MAKEOPTS, SCONSOPTS, or pass it
> straight to escons. no cache confusion or desync between the vars.
Ok, but will use ${SCONSOPTS-$(scons_clean_makeopts)} instead.
The point is that the user can decide to have different SCONSOPTS set
in his/her make.conf, and he/she couldn't magically drop MAKEOPTS for
SCons ebuilds then.
Additionally, I will implement the cache in scons_clean_makeopts().
That should work just fine.
--
Best regards,
Michał Górny
<http://mgorny.alt.pl>
<xmpp:[email protected]>
signature.asc
Description: PGP signature
