On Sat, 18 Oct 2014 21:50:11 +0100, David W Noon wrote: > > 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. > > One can also use /etc/portage/bashrc and enable epatch_user on all > ebuilds. But neither of these is what I want.
I think globally enabling it in bashrc is a little too risky for me. I only use that file to register a die hook so I know when an ebuild fails. > I put the src_prepare() function into the specific ebuilds that I want > to install patches, and I avoid having it in ebuilds where I don't > want patches applied. Isn't that the point of /etc/portage/env? You can enable what you want when you want. Either for all versions of a package or only one. > I accept that this is not a normal user's use case, but I'm not really > a normal user. Normal is optional, do whatever works for you. I sometimes use portage/env and sometimes copy the ebuild to my local overlay for modification. Each case is different. -- Neil Bothwick A good pun is its own reword.
signature.asc
Description: PGP signature
