Hi Stefan, > > Personally I like to see the bluez-utils package vanish and we are just > > using bluez as main package name. Adding a virtual package bluetooth > > that install all BlueZ packages would be nice to have, too. > > > > This would result in the following package names: > > > > bluez > > bluez-libs > > bluez-libs-devel > > bluez-cups > > bluez-alsa > > bluez-gstreamer > > I like that too. I'd probably call it just "bluez-devel", since I won't have a > bluez-libs (and libbluetooth3-devel is bad). > > What's important for me is that it is somehow consistent across distributions > (which might also make it easier for you, in case the usual "cannot compile > $foo" complaint is on the list, just tell them "install bluez-devel or > bluez-libs-devel", no need to check which distribution the reporter is > actually using). > > So for now I'll go for the above list of packages, with libbluetooth3 instead > of bluez-libs. the Fedora packaging guidelines are kinda clear about how to name library packages. Same as for Debian. I don't know about SuSE. This is basically about the build dependencies and changing the devel package name means that you would need to adjust all sources relying on it. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
