| 1 |
On Wednesday, April 18, 2012 9:10:02 PM UTC+3, Mike Frysinger wrote: |
| 2 |
> it isn't uncommon for people to want to force the patch (-p#) or fuzz (-f#) |
| 3 |
> level when applying specific patches. but it is unusual that they want to kill |
| 4 |
> off the extra options: -g0 -E --no-backup-if-mismatch. so i'd like to split |
| 5 |
> these off and improve the epatch API. |
| 6 |
|
| 7 |
LOL mike, i'm fighting with this thing at the very moment. there's a |
| 8 |
patch i received that has whitespace issues and i'd like to specify |
| 9 |
custom EPATCH_OPTS. |
| 10 |
|
| 11 |
i applied the patch to my eclass overlay, and einfo is showing that the |
| 12 |
new eclass is used. |
| 13 |
|
| 14 |
$ EPATCH_OPTS="--ignore-whitespace" emerge -va pf-sources |
| 15 |
|
| 16 |
isn't achieved though. if i do: |
| 17 |
|
| 18 |
236 EPATCH_OPTS="${EPATCH_OPTS}" |
| 19 |
|
| 20 |
everything works as expected. do you mean "cmdline" as in only within |
| 21 |
ebuild? what's the optimal way here? i was desperately searching for |
| 22 |
PATCHCOMMAND in "man make.conf", but this definitely would do the job |
| 23 |
for me. |
Archives