-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 18 Oct 2014 21:18:36 +0100, Neil Bothwick (n...@digimed.co.uk) wrote about "Re: [gentoo-user] Re: XFCE weather plugin does not work" (in <20141018211836.63981...@digimed.co.uk>):
> 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. One can also use /etc/portage/bashrc and enable epatch_user on all ebuilds. But neither of these is what I want. 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. The reason for this is that I create quite a few patches overall. Many of these are a bit flakey, so I don't want them applied to what I view as a production system, except under controlled circumstances. To that end, I maintain my own Portage tree, exempted from emerge --sync, that has the epatch_user included in its ebuilds where needed. This, in turn, allows me to keep experimental patches in /etc/portage/patches without the threat of them turning up in a normal emerge run. I accept that this is not a normal user's use case, but I'm not really a normal user. - -- Regards, Dave [RLU #314465] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* dwn...@ntlworld.com (David W Noon) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlRC0oMACgkQRQ2Fs59Psv+H1ACfQ4mIJl8ie5JIwVtLwOImjOii DTQAnR8SmAg/P/hrtcanyDHm+0K+O9z0 =iaRu -----END PGP SIGNATURE-----