Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: linux.gentoo.dev@...
From: Leho Kraav <leho@...>
Subject: Re: epatch: splitting out common options from user-specific ones
Date: Fri, 20 Apr 2012 12:38:19 -0700 (PDT)
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. 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".


Replies:
Re: epatch: splitting out common options from user-specific ones
-- Leho Kraav
Re: epatch: splitting out common options from user-specific ones
-- Mike Frysinger
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
gnome2 and gnome2-utils eclass changes
Next by thread:
Re: epatch: splitting out common options from user-specific ones
Previous by date:
Re: RFC: Add new remote-id types in metadata.dtd
Next by date:
Re: epatch: splitting out common options from user-specific ones


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.