Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-20 Thread Mike Frysinger
On Friday 20 April 2012 16:06:02 Leho Kraav wrote: > On 20.04.2012 22:59, Mike Frysinger wrote: > > i just committed it since no one responded. so sync up. > > > >> $ EPATCH_OPTS="--ignore-whitespace" emerge -va pf-sources > > > > that's not the intention. EPATCH_OPTS modification should be ins

Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-20 Thread Leho Kraav
On 20.04.2012 22:59, Mike Frysinger wrote: i just committed it since no one responded. so sync up. $ EPATCH_OPTS="--ignore-whitespace" emerge -va pf-sources that's not the intention. EPATCH_OPTS modification should be inside the ebuild. I can't see how having this available could hurt any

Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-20 Thread Leho Kraav
On Wednesday, April 18, 2012 9:10:02 PM UTC+3, Mike Frysinger wrote: it isn't uncommon for people to want to force the patch (-p#) or fuzz (-f#) level when applying specific patches. but it is unusual that they want to kill off the extra options: -g0 -E --no-backup-if-mismatch. so i'd like to s

Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-20 Thread Mike Frysinger
On Friday 20 April 2012 15:38:19 Leho Kraav wrote: > On Wednesday, April 18, 2012 9:10:02 PM UTC+3, Mike Frysinger wrote: > > it isn't uncommon for people to want to force the patch (-p#) or fuzz > > (-f#) level when applying specific patches. but it is unusual that they > > want to kill off the e

Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-20 Thread Leho Kraav
On Wednesday, April 18, 2012 9:10:02 PM UTC+3, Mike Frysinger wrote: > it isn't uncommon for people to want to force the patch (-p#) or fuzz (-f#) > level when applying specific patches. but it is unusual that they want to > kill > off the extra options: -g0 -E --no-backup-if-mismatch. so i'd

Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-19 Thread Mike Frysinger
On Thursday 19 April 2012 23:24:19 Mike Frysinger wrote: > @@ -445,6 +473,7 @@ epatch() { > local patch_cmd > while [[ ${count} -lt 5 ]] ; do > patch_cmd="${BASH_ALIASES[patch]:-patch} -p${count} > +einfo $patch_cmd > > # Gen

Re: [gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-19 Thread Mike Frysinger
no complaints, so here's the patch. precedence order is EPATCH_COMMON_OPTS then EPATCH_OPTS then whatever has been specified on the cmdline. so you can do: EPATCH_OPTS="-F0" epatch epatch -p0 epatch (more for highlighting precedence than a realistic use case) -m

[gentoo-dev] epatch: splitting out common options from user-specific ones

2012-04-18 Thread Mike Frysinger
it isn't uncommon for people to want to force the patch (-p#) or fuzz (-f#) level when applying specific patches. but it is unusual that they want to kill off the extra options: -g0 -E --no-backup-if-mismatch. so i'd like to split these off and improve the epatch API. # Extra options to pass