1 |
Hello |
2 |
|
3 |
Let my explain the problem and my suggestion to handle it better (at |
4 |
least from my point of view) with an example: |
5 |
|
6 |
Sometime ago I bumped bluez version from 4.39-r2 to 4.60, with that |
7 |
bump, a new and *optional* RDEPEND on sys-libs/libcap-ng was added. |
8 |
Since libcap-ng was not keyworded in all arches but x86 and amd64, I had |
9 |
to drop keywords for bluez and open |
10 |
http://bugs.gentoo.org/show_bug.cgi?id=303527 for handling it. |
11 |
|
12 |
From my point of view, I would prefer to: |
13 |
1. Mask "caps" for net-wireless/bluez on affected arches, letting us to |
14 |
keep bluez keyworded. |
15 |
2. Open two bug reports as done with current policy: one for keywording |
16 |
libcap-ng and other to check bluez works ok with it asking arch team to |
17 |
unmask that USE flag if possible. |
18 |
|
19 |
This way to go would have the advantage of letting people running bluez |
20 |
on affected arches to still get the latest bluez version instead of |
21 |
still having to run a pretty old (and buggy) one. |
22 |
|
23 |
Thanks for considering it |