1 |
>>>>> On Wed, 07 Feb 2018, Michał Górny wrote: |
2 |
|
3 |
>> -# @FUNCTION: bzr_src_prepare |
4 |
>> -# @DESCRIPTION: |
5 |
>> -# Default src_prepare(), calls bzr_bootstrap. |
6 |
>> -bzr_src_prepare() { |
7 |
>> - bzr_bootstrap |
8 |
>> } |
9 |
|
10 |
> Hmm, unless I'm mistaken, this can cause another definition |
11 |
> of src_prepare to start applying to ebuilds. |
12 |
|
13 |
That's right, but wasn't relying on inherit order considered a QA |
14 |
violation? In other words, shouldn't an ebuild define an explicit |
15 |
phase function if it inherits more than one eclass exporting that |
16 |
function? |
17 |
|
18 |
> You can submit a PR with this change to get md5-cache with exported |
19 |
> phase data suitable for comparison. |
20 |
|
21 |
> Or... given the popularity of the eclass, you can check by hand ;-P. |
22 |
|
23 |
Done so for the Gentoo repo (before posting the patch). Or rather, |
24 |
I have checked that WORKDIR has identical contents after the prepare |
25 |
phase. |
26 |
|
27 |
Ulrich |