1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
On 07/17/2013 11:55 PM, Rick "Zero_Chaos" Farina wrote: |
5 |
> |
6 |
> |
7 |
> It is my understanding that if you directly use a function from an |
8 |
> eclass you are REQUIRED to inherit that eclass. Given that kind |
9 |
> of sanity would have prevented these failures I find it difficult |
10 |
> to believe my understanding is wrong, but I am willing to learn. |
11 |
> |
12 |
> I think I'll start inheriting base.eclass so I can use multilib |
13 |
> functions. I mean, base.eclass inherits eutils.eclass which |
14 |
> inherits multilib.eclass so it should work out fine, right? |
15 |
> |
16 |
|
17 |
You are wrong. What matters is the API of an eclass and how it is defined. |
18 |
|
19 |
There is no such definition of base.eclass guaranteeing that it will |
20 |
always either a) inherit eutils.eclass or b) provide certain functions |
21 |
from eutils.eclass (maybe by defining them directly in the future). |
22 |
-----BEGIN PGP SIGNATURE----- |
23 |
Version: GnuPG v2.0.20 (GNU/Linux) |
24 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
25 |
|
26 |
iQEcBAEBAgAGBQJR5xd0AAoJEFpvPKfnPDWzaxQH/0HZgEuSFwxO9yAwktAFLlW4 |
27 |
FdvNaUS+bn1oYGi/0vr/7E/j17ZH5/0nych/kw7kOa6009BpBjzdmDeAeZhIGI3n |
28 |
tGGJtYNAsnZ16Rp7yrD0IZNj71ozSiLr6cBJs6m4rpOEJls9O0I1qazxnD+45o6W |
29 |
iPfiDpfcUPFmTa/P3PJ69lAlNQA3EymmKXfB5SJdbt3QELxQR6wGdnpfrev0ieiG |
30 |
gwpmzQzVjgt/PBpw4+tH/HFNdEXF+YjfbGGXoYNkO0FS+GppMtKaTYLEzbLPVORz |
31 |
1v1oBWw/Ysz7CYML1C5R+uZpbf8cZK26mrQMj5gOSeyem/o5vgD7R3uhHFAgsgs= |
32 |
=7JSh |
33 |
-----END PGP SIGNATURE----- |