1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On Sat, 18 Oct 2014 21:18:36 +0100, Neil Bothwick (neil@××××××××××.uk) |
5 |
wrote about "Re: [gentoo-user] Re: XFCE weather plugin does not work" |
6 |
(in <20141018211836.63981584@××××××××××.uk>): |
7 |
|
8 |
> On Sat, 18 Oct 2014 17:18:34 +0100, David W Noon wrote: |
9 |
> |
10 |
>>>> I have not done this relying on the promise by Greg Kubaryk |
11 |
>>>> that the ebuild is epatch_user enabled. |
12 |
>> |
13 |
>> That can be a bit variable. I still put the epatch_user command |
14 |
>> in explicitly, just to be certain. |
15 |
> |
16 |
> You don't need to modify the ebuild to do that. Put this in |
17 |
> /etc/portage/env/category/package |
18 |
> |
19 |
> post_src_unpack() { cd "${S}" epatch_user } |
20 |
> |
21 |
> You can use unpack or prepare. The difference is that the former |
22 |
> runs immediately before the prepare function in the ebuild, the |
23 |
> latter immediately after. Not only does it save manifesting the |
24 |
> ebuild each time you modify it, it saves having the remember to |
25 |
> modify it at all after an update. More importantly, your work is |
26 |
> not destroyed on the next sync. |
27 |
|
28 |
One can also use /etc/portage/bashrc and enable epatch_user on all |
29 |
ebuilds. But neither of these is what I want. |
30 |
|
31 |
I put the src_prepare() function into the specific ebuilds that I want |
32 |
to install patches, and I avoid having it in ebuilds where I don't |
33 |
want patches applied. The reason for this is that I create quite a |
34 |
few patches overall. Many of these are a bit flakey, so I don't want |
35 |
them applied to what I view as a production system, except under |
36 |
controlled circumstances. To that end, I maintain my own Portage |
37 |
tree, exempted from emerge --sync, that has the epatch_user included |
38 |
in its ebuilds where needed. This, in turn, allows me to keep |
39 |
experimental patches in /etc/portage/patches without the threat of |
40 |
them turning up in a normal emerge run. |
41 |
|
42 |
I accept that this is not a normal user's use case, but I'm not really |
43 |
a normal user. |
44 |
- -- |
45 |
Regards, |
46 |
|
47 |
Dave [RLU #314465] |
48 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
49 |
dwnoon@××××××××.com (David W Noon) |
50 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
51 |
-----BEGIN PGP SIGNATURE----- |
52 |
Version: GnuPG v2 |
53 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
54 |
|
55 |
iEYEARECAAYFAlRC0oMACgkQRQ2Fs59Psv+H1ACfQ4mIJl8ie5JIwVtLwOImjOii |
56 |
DTQAnR8SmAg/P/hrtcanyDHm+0K+O9z0 |
57 |
=iaRu |
58 |
-----END PGP SIGNATURE----- |