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