There is a bit of a strange situation going on with bluedevil and libbluedevil. Bluedevil is not yet at a stable release. Libbluedevil, though, is apparently at a stable release (1.8). So it makes sense keeping bluedevil in playground and keeping it in sync with git, but libbluedevil is a bit more questionable. However, libbluedevil is currently pretty much useless with bluedevil, since that is the only application making use of it in the openSUSE repos. So to me that makes the question of whether we should have libbluedevil in playground, extra, or distro less clear. Kbluetooth, which bluedevil is intended to replace, is in Distro, but there isn't any software making use of bluedevil in Distro. However, once bluedevil is stable, which doesn't seem like it will be that much longer, I assume it will be moved to Distro. You could always move them both together, but the way buildservice operates there really doesn't seem to be any benefit to that unless the plan is to move both to Extra (which I don't think is a good idea since bluetooth support is pretty essential and kbluetooth is essentially obselete). We can't get rid of kbluetooth yet because bluedevil still does not work for as many devices as kbluetooth and isn't entirely stable. If libbluedevil does stay in playground, that also leads to the question of whether it should follow the stable releases or keep with the git snapshots. Snapshots are in line with having it in playground, but may not be as stable as the official releases. Further, currently the latest git snapshot of libbluedevil in playground is older than the latest official stable release. I set up my own build that uses the stable release, but there is no point submitting it if the plan is to stick with the git snapshots. Any thoughts? -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org