public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Leho Kraav <leho@kraav.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] epatch: splitting out common options from user-specific ones
Date: Fri, 20 Apr 2012 22:54:32 +0300	[thread overview]
Message-ID: <4F91BEF8.7080409@kraav.com> (raw)
In-Reply-To: <25544530.1346.1334950699692.JavaMail.geo-discussion-forums@vbpz13>

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 split
> these off and improve the epatch API.

LOL mike, i'm fighting with this thing at the very moment. there's a 
patch i received that has whitespace issues and i'd like to specify 
custom EPATCH_OPTS.

i applied the patch to my eclass overlay, and einfo is showing that the 
new eclass is used.

$ EPATCH_OPTS="--ignore-whitespace" emerge -va pf-sources

isn't achieved though. if i do:

236 EPATCH_OPTS="${EPATCH_OPTS}"

everything works as expected. do you mean "cmdline" as in only within 
ebuild? what's the optimal way here? i was desperately searching for 
PATCHCOMMAND in "man make.conf", but this definitely would do the job 
for me.



  reply	other threads:[~2012-04-20 20:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <iRHui-2kD-3@gated-at.bofh.it>
2012-04-20 19:38 ` [gentoo-dev] epatch: splitting out common options from user-specific ones Leho Kraav
2012-04-20 19:54   ` Leho Kraav [this message]
2012-04-20 19:59   ` Mike Frysinger
2012-04-20 20:06     ` Leho Kraav
2012-04-20 21:40       ` Mike Frysinger
2012-04-18 18:03 Mike Frysinger
2012-04-20  3:24 ` Mike Frysinger
2012-04-20  3:38   ` Mike Frysinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F91BEF8.7080409@kraav.com \
    --to=leho@kraav.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox