<phant0mas>mark_weaver: anything on my yesterday question? :-)
<mark_weaver>phant0mas: three possible suggestions: (1) the option may not be needed, because of the CPATH environment variable which will already be set; (2) you could patch the configure script to allow the two headers directories to be specified separately (I'd guess it is just used to make a -I option; (3) you could add a phase before configure that copies the includes from both dirs into one dir.
<mark_weaver>so you either build in a separate build dir, in which case a symlink to it is probably okay, or copy it.
<mark_weaver>if the primary source code you're building is from git-fetch, then I'd guess it should be sufficient to just create a build dir, chdir to it, and then run the configure script in the (immutable) source dir in the store.
<mark_weaver>I guess the default 'unpack' and 'configure' phases could check to see if the source is a directory, and if so, do the right thing.
<civodul>mark_weaver: i think 'patches' works on git-fetch origins, but only in core-updates (commit 3ca00bb51e3ff906a700b6925e0ce81558c8c469)