On 04/02/2014 16:47, Rich Freeman wrote: > On Wed, Apr 2, 2014 at 4:27 PM, Rick "Zero_Chaos" Farina > <[email protected]> wrote: >> Honestly I'd rather see this split up into libbluetooth and bluez than >> make it possible to build a nearly entirely crippled bluez with no udev >> support. > > I think the right approach really depends on usefulness. Splitting > packages has its own set of issues. If it really made sense in the > general case to install one without the other splitting would make > managing dependencies a lot cleaner. However, if this is really so > that 10 Gentoo users can avoid having udev installed just give them a > flag and a warning and let them keep the pieces if they break their > box.
I guess this is more of a question to be asked to the bluez developers why they even allow the bluez configure script to make udev optional. If they put that in there, there must be a good reason for it. So in one way, we're simply exposing additional functionality already in the package. > I mean, who is going to set USE=-udev globally and not expect that > something could go wrong? Anybody who is going to set up busybox mdev > isn't going to try to make that switch over their lunch break on a > production box. Actually, it took me about an hour to migrate off of udev. Most of the little problems left over were packages I forgot to rebuild w/ USE="-udev". I've either done that, or set package-specific USE flags to cut udev out when needed. Setup a VM and try it. See what life is like on the other side! -- Joshua Kinard Gentoo/MIPS [email protected] 4096R/D25D95E3 2011-03-28 "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between." --Emperor Turhan, Centauri Republic
