| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 25/10/12 12:41 PM, hasufell wrote: |
| 5 |
> 6. How can I make the python dependencies optional, e.g. that |
| 6 |
> python:3.2 is only pulled in when gtk useflag for this package is |
| 7 |
> set? |
| 8 |
|
| 9 |
that's not so much an optional dependency as an enforcement of a |
| 10 |
PYHTON_TARGETS, isn't it? or is it the other way around, ie, |
| 11 |
PYTHON_COMPAT="python3.2" is not possible unless USE="+gtk" ? |
| 12 |
|
| 13 |
|
| 14 |
Afaik the way python-r1 and distutils-r1 is meant to work is that |
| 15 |
it'll build for whatever is supplied in PYTHON_TARGETS , in accordance |
| 16 |
with whatever is in PYTHON_COMPAT. It's supposed to be a complete |
| 17 |
set, though. So if python-3.2 is in both TARGETS and COMPAT then it's |
| 18 |
built for that, otherwise it isn't. For your USE=gtk issue , either |
| 19 |
you would need to complain via either |
| 20 |
|
| 21 |
REQUIRED_USE="gtk? ( python_targets_python3_2 )" |
| 22 |
|
| 23 |
or |
| 24 |
|
| 25 |
REQUIRED_USE="python_targets_python3_2? ( gtk )" |
| 26 |
|
| 27 |
..depending on which situation applies. |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 30 |
|
| 31 |
iF4EAREIAAYFAlCJcoUACgkQ2ugaI38ACPA1lgD+KuSlC92KqsnHcePQJhtJCGY2 |
| 32 |
iXGhvboB2h1qlHoPAEUA/jP/XcWmjaRSjIxtEJMUqq76qqqMCaBwphrMBkbReGVT |
| 33 |
=euK2 |
| 34 |
-----END PGP SIGNATURE----- |
Archives