From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Kent Fredric <kentfredric@gmail.com>
Subject: Re: [gentoo-dev] eutils.eclass / EPATCH_EXCLUDE defined wrong?
Date: Fri, 17 Aug 2012 23:12:49 -0400 [thread overview]
Message-ID: <201208172312.50586.vapier@gentoo.org> (raw)
In-Reply-To: <CAATnKFDD3DDKWPYXHP8u83K9HGZqWRxj3aaZ5asG_FpoYBSFvQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 506 bytes --]
On Monday 06 August 2012 15:45:46 Kent Fredric wrote:
> Looking at the source of eutils.eclass ' # Let people filter things
> dynamically ' suggests to me that this field is for use by a end user
> via package.env and friends.
no, it is meant for packagers to have a single patch tarball, setup
EPATCH_EXCLUDE based on USE flags, and then run epatch on that one dir.
otherwise, you'd have to `rm` files.
there is no support for end users discarding selective patches via package.env
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-08-18 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 19:45 [gentoo-dev] eutils.eclass / EPATCH_EXCLUDE defined wrong? Kent Fredric
2012-08-18 3:12 ` Mike Frysinger [this message]
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=201208172312.50586.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=kentfredric@gmail.com \
/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