El lun, 19-08-2013 a las 10:30 -0400, Ian Stakenvicius escribió: > On 19/08/13 08:49 AM, Pacho Ramos wrote: > > I have seen some ebuilds (just seen bluez one) that are using > > "consolekit" USE flag to not force plugdev group usage (as it's not > > used on consolekit/logind setups). The problem is that this is > > common with systemd/logind then, people merging bluez, will want > > this "consolekit" USE flag enabled. > > > > Should we have a more generic USE flag for covering > > consolekit/logind? Should we use a USE flag for plugdev group usage > > (since most users will be using either consolekit or systemd)? > > > > Thanks for your help > > > > > > For this particular case, and just looking at the package itself, it > seems to make sense to reverse the flag -- have a USE="plugdev" for > plugdev group install and otherwise don't (for consolekit/systemd > support). > > Of course, managing this via default profiles makes things a bit more > difficult since desktop/ isn't auto-enabling a flag anymore. Does the > 'consolekit' flag just stop plugdev-group usage or does it also set a > ./configure option for alternative code? If the latter, perhaps a > second use flag 'logind' would be useful and then both flags can > disable plugdev-group (and the logind one obviously won't configure > bluez for CK) >
It's the first case: it drops plugdev group usage
