1 |
I'm at a loss to explain why this is a good idea or desirable: |
2 |
|
3 |
!!! The ebuild selected to satisfy |
4 |
">=net-libs/gupnp-0.18[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?]" |
5 |
has unmet requirements. |
6 |
- net-libs/gupnp-0.20.12-r1::gentoo USE="introspection -connman |
7 |
-networkmanager" ABI_X86="64 -32 -x32" PYTHON_TARGETS="python2_7 -python2_6" |
8 |
|
9 |
The following REQUIRED_USE flag constraints are unsatisfied: |
10 |
exactly-one-of ( connman networkmanager ) |
11 |
|
12 |
|
13 |
|
14 |
USE="upnp" is pulling this in, the major user of that flag here is |
15 |
farstream. |
16 |
|
17 |
Maybe I want farstream. Maybe I want upnp for it. |
18 |
Maybe I don't care for connman or networkmanager (I use wicd, some users |
19 |
want no nw manager at all) |
20 |
|
21 |
So, what is the sense behind a feature of an instant messenger framework |
22 |
causing me to decide between two undesirable connection managers? |
23 |
|
24 |
Anyone see some valid logic that I miss? |
25 |
|
26 |
|
27 |
-- |
28 |
Alan McKinnon |
29 |
alan.mckinnon@×××××.com |