| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 12/11/2013 07:54 PM, Greg Turner wrote: |
| 5 |
> On Wed, Dec 11, 2013 at 2:01 PM, hasufell <hasufell@g.o> wrote: |
| 6 |
>> I actually feel that some parts of this is not documentation, but rather "wiki". So maybe |
| 7 |
>> that's exactly where to put it? |
| 8 |
>> |
| 9 |
>> The doc in the eclass should only describe the behavior of the eclass and the main points you |
| 10 |
>> need to know in order to get it going. |
| 11 |
>> |
| 12 |
>> But it is not a strong feeling. |
| 13 |
> |
| 14 |
> I think you're probably right... I'll endeavor to re-factor this patch and put the wiki stuff |
| 15 |
> into the wiki. |
| 16 |
> |
| 17 |
>>> +# it is often best to put multilib-minimal first on the inherits list. |
| 18 |
>> |
| 19 |
>> first? You mean last or what? |
| 20 |
> |
| 21 |
> I definitely meant first -- the existing in-source doc said "last" but I thought that must |
| 22 |
> surely be a thinko... unless my understanding of how inherits works is backwards -- the first, |
| 23 |
> not the last, inheritee gets the default phase-function implementations wired up to it, |
| 24 |
> correct? I suppose another assumption I have, that, if not shared, might be leading us to |
| 25 |
> opposite conclusions, is that a majority of inheritors would want the default phase function |
| 26 |
> implementations to be wired up to multilib-minimal...? |
| 27 |
> |
| 28 |
> btw, based on the same criteria you mention above, some of what I've said about the matter |
| 29 |
> probably better belongs in the wiki rather than the in-source doc. |
| 30 |
> |
| 31 |
> -gmt |
| 32 |
> |
| 33 |
> |
| 34 |
|
| 35 |
The *last* eclass inherited that exports a particular function (via EXPORT_FUNCTIONS) is the one |
| 36 |
that prevails, not the *first*. Therefore, if it is expected that multilib-minimal.eclass's |
| 37 |
versions will be used, it should be nearer the end of the inherit line, not the beginning. |
| 38 |
|
| 39 |
- -- |
| 40 |
Jonathan Callen |
| 41 |
-----BEGIN PGP SIGNATURE----- |
| 42 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 43 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 44 |
|
| 45 |
iQIcBAEBCgAGBQJSqSBrAAoJELHSF2kinlg4JcgP/2KKiXTcRkBUQmT0A5X0NLJV |
| 46 |
TqthtEKHlQhAuc9VjVtMj+h1UhAuDxsK4tasUBlXG6b3ab3o5drXVyD+rZWJHr8N |
| 47 |
FaqWuwSsbnIxp461DNVbQk5vhHAHY9oxFxT1rV/wjgFIK0d6yZxSBBDWWtWLbOba |
| 48 |
ev/FRw5LqnK8JkX/YaGCo6HYNSxaSGTRdeuSlndfF5dLYXRFO5JIR98S6YtsZWFY |
| 49 |
jXjKNcYQNVX/HAeU42LCMffgODSiCmLQPE9D5vhP9hOD9tLlBe6WZLt8iKKaBOug |
| 50 |
rBvRaQq9lL7obivYohMqR+7MCeCcvlDc6rMu1ZEdBMEfN39lzmTiAp9wXlYpbB7Q |
| 51 |
pM1YI97bqXGwS8lpBL6AIkS5Uep/0q1UD8bDw67PMtOrCh5Oi/SniCY8pdZCqpms |
| 52 |
bFYp+MgtYtvopI+vtn1P7/P4LBv9LspReQ7lVV4ukKSkuqx7L4B3Az3fiHcTV8ce |
| 53 |
XCzbSkR4ZOwvAypXtMRhmfcpIchVegqLwUIZHVRkUH9Qwd+o4dvpmBIxkUVdqFJD |
| 54 |
OINNplQ1/WqxJdonkFVzWUAO1jE67M91uf3zcimB63ioNKwSQGalVGQt3Rp1RfCd |
| 55 |
eJgsgkmtvI8fqhnkZTO+i70Xl89+JXhz+R4tfMewTId4wch+w3EiX3PKJUbF9rWK |
| 56 |
P6tuUW0eRNp6t7SU2ZdY |
| 57 |
=WMyy |
| 58 |
-----END PGP SIGNATURE----- |
Archives