Hi guys,
I would like to push Bluez 5 to the repos, and rename Bluez 4 to 'bluez4'. Some things still require Bluez 4, and the two can not be installed together, so this is how I propose to do it.
We will have the following packages:
bluez4: the bluetooth daemon, providing the old dbus interface (a pared down version of our current 'bluez' package) bluez: the bluetooth daemon, providing the new dbus interface (not backwards compatible) bluez-libs: the libraries split off from the bluez package (backwards compatible) bluez-utils: the (development and testing) tools split off from the bluez package (backwards compatible)
All packages currently depending on 'bluez' will have to be rebuilt to depend on 'bluez-libs' (most packages), 'bluez4' (at least libbluedevil) or 'bluez' (if anything has support for this). Packages that simply makedepend do not need to be rebuilt, just change the dependency in SVN (there is no soname bump).
Any objections?
Cheers,
Tom
On Mon, May 13, 2013 at 6:02 PM, Tom Gundersen teg@jklm.no wrote:
I would like to push Bluez 5 to the repos, and rename Bluez 4 to 'bluez4'. Some things still require Bluez 4, and the two can not be installed together, so this is how I propose to do it.
We will have the following packages:
bluez4: the bluetooth daemon, providing the old dbus interface (a pared down version of our current 'bluez' package) bluez: the bluetooth daemon, providing the new dbus interface (not backwards compatible) bluez-libs: the libraries split off from the bluez package (backwards compatible) bluez-utils: the (development and testing) tools split off from the bluez package (backwards compatible)
All packages currently depending on 'bluez' will have to be rebuilt to depend on 'bluez-libs' (most packages), 'bluez4' (at least libbluedevil) or 'bluez' (if anything has support for this). Packages that simply makedepend do not need to be rebuilt, just change the dependency in SVN (there is no soname bump).
I put bluez/bluez4 in [staging] so we can move ahead with this.
-t
Am 01.06.2013 11:23, schrieb Tom Gundersen:
On Mon, May 13, 2013 at 6:02 PM, Tom Gundersen teg@jklm.no wrote:
I would like to push Bluez 5 to the repos, and rename Bluez 4 to 'bluez4'. Some things still require Bluez 4, and the two can not be installed together, so this is how I propose to do it.
We will have the following packages:
bluez4: the bluetooth daemon, providing the old dbus interface (a pared down version of our current 'bluez' package) bluez: the bluetooth daemon, providing the new dbus interface (not backwards compatible) bluez-libs: the libraries split off from the bluez package (backwards compatible) bluez-utils: the (development and testing) tools split off from the bluez package (backwards compatible)
All packages currently depending on 'bluez' will have to be rebuilt to depend on 'bluez-libs' (most packages), 'bluez4' (at least libbluedevil) or 'bluez' (if anything has support for this). Packages that simply makedepend do not need to be rebuilt, just change the dependency in SVN (there is no soname bump).
I put bluez/bluez4 in [staging] so we can move ahead with this.
-t
Please don't move qemu with bluez move. qemu 1.5.0 is a bit to buggy to leave testing repository. If you move i'll bump extra 1.4.x with correct depends.
greetings tpowa
On Thu, Jun 6, 2013 at 7:38 AM, Tobias Powalowski tobias.powalowski@googlemail.com wrote:
Please don't move qemu with bluez move. qemu 1.5.0 is a bit to buggy to leave testing repository. If you move i'll bump extra 1.4.x with correct depends.
I guess you could put qemu 1.4.1-4 with correct depends into [staging] right now, so that it's ready to be moved right to [extra] once bluez 5 leaves [testing].
Am 06.06.2013 07:49, schrieb Jan Alexander Steffens:
On Thu, Jun 6, 2013 at 7:38 AM, Tobias Powalowski tobias.powalowski@googlemail.com wrote:
Please don't move qemu with bluez move. qemu 1.5.0 is a bit to buggy to leave testing repository. If you move i'll bump extra 1.4.x with correct depends.
I guess you could put qemu 1.4.1-4 with correct depends into [staging] right now, so that it's ready to be moved right to [extra] once bluez 5 leaves [testing].
Done added to staging repository.
On Thu, Jun 6, 2013 at 9:15 AM, Tobias Powalowski tobias.powalowski@googlemail.com wrote:
Am 06.06.2013 07:49, schrieb Jan Alexander Steffens:
On Thu, Jun 6, 2013 at 7:38 AM, Tobias Powalowski tobias.powalowski@googlemail.com wrote:
Please don't move qemu with bluez move. qemu 1.5.0 is a bit to buggy to leave testing repository. If you move i'll bump extra 1.4.x with correct depends.
I guess you could put qemu 1.4.1-4 with correct depends into [staging] right now, so that it's ready to be moved right to [extra] once bluez 5 leaves [testing].
Done added to staging repository.
Thanks for the heads up!
Cheers,
Tom
On Mon, May 13, 2013 at 6:02 PM, Tom Gundersen teg@jklm.no wrote:
I would like to push Bluez 5 to the repos, and rename Bluez 4 to 'bluez4'. Some things still require Bluez 4, and the two can not be installed together, so this is how I propose to do it.
We will have the following packages:
bluez4: the bluetooth daemon, providing the old dbus interface (a pared down version of our current 'bluez' package) bluez: the bluetooth daemon, providing the new dbus interface (not backwards compatible) bluez-libs: the libraries split off from the bluez package (backwards compatible) bluez-utils: the (development and testing) tools split off from the bluez package (backwards compatible)
All packages currently depending on 'bluez' will have to be rebuilt to depend on 'bluez-libs' (most packages), 'bluez4' (at least libbluedevil) or 'bluez' (if anything has support for this). Packages that simply makedepend do not need to be rebuilt, just change the dependency in SVN (there is no soname bump).
bluez-5 and bluez4 have now moved to extra.
-t
arch-dev-public@lists.archlinux.org