| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 19/08/13 08:49 AM, Pacho Ramos wrote: |
| 5 |
> I have seen some ebuilds (just seen bluez one) that are using |
| 6 |
> "consolekit" USE flag to not force plugdev group usage (as it's not |
| 7 |
> used on consolekit/logind setups). The problem is that this is |
| 8 |
> common with systemd/logind then, people merging bluez, will want |
| 9 |
> this "consolekit" USE flag enabled. |
| 10 |
> |
| 11 |
> Should we have a more generic USE flag for covering |
| 12 |
> consolekit/logind? Should we use a USE flag for plugdev group usage |
| 13 |
> (since most users will be using either consolekit or systemd)? |
| 14 |
> |
| 15 |
> Thanks for your help |
| 16 |
> |
| 17 |
> |
| 18 |
|
| 19 |
For this particular case, and just looking at the package itself, it |
| 20 |
seems to make sense to reverse the flag -- have a USE="plugdev" for |
| 21 |
plugdev group install and otherwise don't (for consolekit/systemd |
| 22 |
support). |
| 23 |
|
| 24 |
Of course, managing this via default profiles makes things a bit more |
| 25 |
difficult since desktop/ isn't auto-enabling a flag anymore. Does the |
| 26 |
'consolekit' flag just stop plugdev-group usage or does it also set a |
| 27 |
./configure option for alternative code? If the latter, perhaps a |
| 28 |
second use flag 'logind' would be useful and then both flags can |
| 29 |
disable plugdev-group (and the logind one obviously won't configure |
| 30 |
bluez for CK) |
| 31 |
|
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.20 (GNU/Linux) |
| 34 |
|
| 35 |
iF4EAREIAAYFAlISK+gACgkQ2ugaI38ACPAbiAEAnm1NLYz8GAJ08lGitdAMWfaa |
| 36 |
OZBpRSIFiBF6WuLKog0A/2qWRVwqY+ubxLrG/6wNIYS5+Ynf4CqyIIDhJ9jTTKHz |
| 37 |
=yQ2r |
| 38 |
-----END PGP SIGNATURE----- |
Archives