1 |
On Sat, 18 Oct 2014 10:03:10 +0300, Gevisz (gevisz@×××××.com) wrote |
2 |
about "Re: [gentoo-user] Re: XFCE weather plugin does not work" (in |
3 |
<544210d1.22a0700a.56bc.5820@×××××××××.com>): |
4 |
|
5 |
On 18/10/14 08:03, Gevisz wrote: |
6 |
[snip] |
7 |
>> I have unpacked your patches to /etc/portage/patches as described here: |
8 |
>> http://wiki.gentoo.org/wiki//etc/portage/patches |
9 |
>> and then run # emerge xfce4-weather-plugin |
10 |
> |
11 |
>> After restarting xfce4, the weather-plugin started to work. Thank you. |
12 |
|
13 |
You're welcome. The Xfce developers did the hard yakka, I simply |
14 |
massaged the patches so that they would apply cleanly on Gentoo systems. |
15 |
|
16 |
>> Nevertheless, just |
17 |
>> # emerge --update --deep --with-bdeps=y --newuse --backtrack=90 --ask world |
18 |
>> instead of # emerge xfce4-weather-plugin |
19 |
>> did not worked. |
20 |
|
21 |
That's because the plugin's version/release number has not been |
22 |
modified, so emerge will not process it. |
23 |
|
24 |
> The ebuild should have the following lines added: |
25 |
> |
26 |
> src_prepare() { |
27 |
> epatch_user |
28 |
> } |
29 |
> |
30 |
>> I have not done this relying on the promise by Greg Kubaryk |
31 |
>> that the ebuild is epatch_user enabled. |
32 |
|
33 |
That can be a bit variable. I still put the epatch_user command in |
34 |
explicitly, just to be certain. |
35 |
|
36 |
> Don't forget to redo the manifest for the ebuild. |
37 |
> |
38 |
>> I never dealt with ebuilds on a maintaner level. |
39 |
>> So, may I ask if it is really necessary and for which purpose. |
40 |
|
41 |
If you modify the ebuild then you *must* update the manifest. If you |
42 |
don't modify the ebuild then there is no need. |
43 |
-- |
44 |
Regards, |
45 |
|
46 |
Dave [RLU #314465] |
47 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
48 |
dwnoon@××××××××.com (David W Noon) |
49 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |