1 |
On 06/20/2012 06:19 AM, Mike Frysinger wrote: |
2 |
> On Tuesday 19 June 2012 22:46:26 Samuli Suominen wrote: |
3 |
>> On 06/15/2012 06:10 PM, Mike Frysinger wrote: |
4 |
>>> On Friday 15 June 2012 03:44:14 Samuli Suominen wrote: |
5 |
>>>> On 06/13/2012 06:02 AM, Mike Frysinger wrote: |
6 |
>>>>> i've noticed a growing trend where people put setup of variables into |
7 |
>>>>> pkg_setup that only matter to src_* funcs presumably so they don't have |
8 |
>>>>> to call the respective src_* func from an inherited eclass. |
9 |
>>>>> unfortunately this adds pointless overhead to binpkgs. can we please |
10 |
>>>>> move away from this practice ? |
11 |
>>>> |
12 |
>>>> Every Xfce ebuild in gentoo-x86 is using pkg_setup() for 3 variables, |
13 |
>>>> DOCS for src_install, PATCHES for src_prepare |
14 |
>>> |
15 |
>>> these are static variables, so defining them in a func is pointless |
16 |
>> |
17 |
>> "sort of" not necessarily, 'has $useflag && PATCHES+=( )' has been used |
18 |
>> before, not sure if it's used in tree right now or not |
19 |
> |
20 |
> as we've always said, USE conditional patches are to be highly discouraged |
21 |
|
22 |
I agree BUT there are cases where it's OK to use conditional patching: |
23 |
|
24 |
For example, libfoo-0.1.1 is broken and is fixed in git for master which |
25 |
will be in next release. The fix doesn't apply to 0.1.1 cleanly without |
26 |
heavy modifications. |
27 |
Then you would take the easiest possible route to get 0.1.1 working |
28 |
again, with the comfort of knowing it's properly fixed for the next version. |
29 |
|
30 |
-Samuli |