Package P bypasses applying user patches (by not calling default_src_prepare). I have patches I need to apply to P, and in this case I really don't want to fork the ebuild. So, I'm hell bent on doing it the hacky way with /etc/portage/bashrc (which, IIRC, I have been told on this list not to do, but now I don't have much choice).
To make it work I need to know how the bashrc file is spliced into the ebuild. For a given ebuild phase PH, does the bashrc code come before the rest of PH, after PH, or does it replace PH? wiki and even the dev guide are silent about this. -- Please don't Cc: me privately on mailing lists and Usenet, if you also post the followup to the list or newsgroup. To reply privately _only_ on Usenet, fetch the TXT record for the domain.
