From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] eutils.eclass / EPATCH_EXCLUDE defined wrong?
Date: Tue, 7 Aug 2012 07:45:46 +1200 [thread overview]
Message-ID: <CAATnKFDD3DDKWPYXHP8u83K9HGZqWRxj3aaZ5asG_FpoYBSFvQ@mail.gmail.com> (raw)
I was goofing around trying to get current dev-vcs/git-9999 building
by skipping the CVS patch ( which is applied with epatch ) and I had a
bizzare amount of time working out how to get it working.
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.
However, every time I ran emerge, the 'environment' file simply
suggests that EPATCH_EXCLUDE was ="" .
Looking elsewhere in eutils.eclass, I spied a forced initialization of
EPATCH_EXCLUDE, which implicitly means you can't actually use this to
exclude patches outside .ebuild
Commenting this line out, yielded the result I had been expecting, the
CVS patch being skipped .
I only thought I could do this because I used something like this
once upon a time with net-im/psi-9999 and thought it was just "normal"
to be able to disable patches if I really wanted to. ( But I see now
they acheive this by copying MY_EPATCH_EXCLUDE to EPATCH_EXCLUDE in
the .ebuild ).
So, is this variable guarded against user tampering intentionally? It
sure beats hacking the ebuild.
( Side note, what would also be nice is some sort of warning if things
you set in package.env are getting totally ignored. But thats a hard
problem )
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"
http://kent-fredric.fox.geek.nz
next reply other threads:[~2012-08-06 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 19:45 Kent Fredric [this message]
2012-08-18 3:12 ` [gentoo-dev] eutils.eclass / EPATCH_EXCLUDE defined wrong? 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=CAATnKFDD3DDKWPYXHP8u83K9HGZqWRxj3aaZ5asG_FpoYBSFvQ@mail.gmail.com \
--to=kentfredric@gmail.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