| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
|
| 5 |
Tiziano Müller wrote: |
| 6 |
| Hi everyone |
| 7 |
| |
| 8 |
| With eapis 1 and 2 we introduced nice features but also a couple of new |
| 9 |
| problems. One of them are the use dependencies when the package you |
| 10 |
| depend on doesn't have the use flag anymore (see [1] for an example). |
| 11 |
Hello all, |
| 12 |
|
| 13 |
~ Now that this topic was brought to light, I would like to add |
| 14 |
another point... |
| 15 |
|
| 16 |
~ I'm not sure if this has been worked out, or I just don't know how |
| 17 |
it is done, but a lot of python packages |
| 18 |
~ need to check use flags for dev-lang/python, like tk or threads for |
| 19 |
example. Now this is tricky considering the slotting of |
| 20 |
~ the interpreter. Let me give you an example: |
| 21 |
|
| 22 |
~ Suppose I have both python-2.5 and python-2.6 installed. python-2.5 |
| 23 |
was installed with tk use flag enabled but python-2.6 has it disabled. |
| 24 |
~ When some package tries to check for foo? ( dev-lang/python[tk] ) |
| 25 |
it will merge nicely because the use dep restriction is achieved with |
| 26 |
python-2.5, even |
| 27 |
~ if python-2.6 is the selected interpreter and it misses the tk use |
| 28 |
flag. Is there a way to workaround this? am I missing something? or is |
| 29 |
just something else |
| 30 |
~ to take into account for next eapi? |
| 31 |
|
| 32 |
|
| 33 |
~ Thanks a lot, |
| 34 |
|
| 35 |
~ Best regards, |
| 36 |
|
| 37 |
~ Jesus Rivero (Neurogeek) |
| 38 |
-----BEGIN PGP SIGNATURE----- |
| 39 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 40 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 41 |
|
| 42 |
iEYEARECAAYFAkmz/lMACgkQdIssYB9vBoPEbwCfYg/BaEhRtNCv1LChbqdAt8RW |
| 43 |
T8oAmwaA6Jz2HX5NbSHhD3XeN7JnqAHL |
| 44 |
=oJr/ |
| 45 |
-----END PGP SIGNATURE----- |
Archives