On Sat, 18 Oct 2014 17:18:34 +0100, David W Noon wrote: > >> I have not done this relying on the promise by Greg Kubaryk > >> that the ebuild is epatch_user enabled. > > That can be a bit variable. I still put the epatch_user command in > explicitly, just to be certain.
You don't need to modify the ebuild to do that. Put this
in /etc/portage/env/category/package
post_src_unpack() {
cd "${S}"
epatch_user
}
You can use unpack or prepare. The difference is that the former runs
immediately before the prepare function in the ebuild, the latter
immediately after. Not only does it save manifesting the ebuild each time
you modify it, it saves having the remember to modify it at all after an
update. More importantly, your work is not destroyed on the next sync.
--
Neil Bothwick
I can't walk on water, but I can stagger on alcohol.
signature.asc
Description: PGP signature
