Re: [SCM] jackd2 packaging branch, master, updated. debian/1.9.5.dfsg-13-18-g7c7e31a
On Tue, Jun 15, 2010 at 15:35:56 (CEST), adiknoth-gu...@users.alioth.debian.org
wrote:
> The following commit has been merged in the master branch:
> commit fe9381f0fa6aacfae772ee91fa53296b67c8a1ce
> Author: Adrian Knoth
> Date: Tue Jun 15 14:46:09 2010 +0200
>
> Rename libjack0 to libjack-jackd2-0 and provide libjack-0.116
>
> diff --git a/debian/control.in b/debian/control.in
> index eb7e9ba..a0f8d97 100644
> --- a/debian/control.in
> +++ b/debian/control.in
> @@ -44,7 +44,7 @@ Description: JACK Audio Connection Kit (server and example
> clients)
> .
> This package contains the daemon jackd as well as some example clients.
>
> -Package: libjack0
> +Package: libjack-jackd2-0
> Architecture: any
> Section: libs
> Depends: ${shlibs:Depends},
> @@ -52,6 +52,7 @@ Depends: ${shlibs:Depends},
> Conflicts: jackd2 (>> ${binary:Version}),
> jackd2 (<< ${binary:Version})
> Suggests: jackd2 (= ${binary:Version})
> +Provides: libjack-0.116
> Description: JACK Audio Connection Kit (libraries)
> JACK is a low-latency sound server, allowing multiple applications to
> connect to one audio device, and to share audio between themselves.
I think both libjack-jackd2-0 and libjack0 must specify all fields
Conflicts, Replaces and Provides on libjack-0.116 to ensure, that
exactly one of the libs is being installed
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] jackd2 packaging branch, master, updated. debian/1.9.5.dfsg-13-18-g7c7e31a
On Tue, Jun 15, 2010 at 04:09:24PM +0200, Reinhard Tartler wrote: > > Huu, this will result in a major usability issue. While it's fine for > > the buildds to always use jackd1, it's inconvenient for users who want > > to run jackd2 AND compile some jack apps on their own. > > If there are better approaches, please let me know. > > How about making jackd2 provide a binary package 'libjack-jackd2-dev' > that conflicts with libjack-dev? Sounds good. Will do. TNX -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] jackd2 packaging branch, master, updated. debian/1.9.5.dfsg-13-18-g7c7e31a
On Tue, Jun 15, 2010 at 15:55:02 (CEST), Adrian Knoth wrote: > On Tue, Jun 15, 2010 at 01:35:54PM +, > adiknoth-gu...@users.alioth.debian.org wrote: > >> The following commit has been merged in the master branch: >> commit 0732d192e10a578b76d9075cdf0136445cae6304 >> Author: Adrian Knoth >> Date: Tue Jun 15 14:38:26 2010 +0200 >> >> Drop libjack-dev from jackd2. >> >> Only jackd1 provides the dev package. > > Huu, this will result in a major usability issue. While it's fine for > the buildds to always use jackd1, it's inconvenient for users who want > to run jackd2 AND compile some jack apps on their own. > > It's a rather common use case, and given that jackd2 will be the default > in squeeze, we need to address this issue. > > > Is there a well-known approach? If not, here are the facts: > > * libjack-dev header files are fine also for jackd2 users > > * /usr/lib/pkgconfig/jack.pc: Dunno. Probably ok. > > * /usr/lib/libjack(server).a: Does anybody care? > > * /usr/lib/libjack(server).so are two symlinks to the full (package > specific) version number, e.g., libjack.so.0.0.28. > > As long as jackd1 and jackd2 don't differ in the SOVERSION, we could > manually symlink libjack.so->libjack.so.0 instead. > > > I guess libjack-dev then needs to depend on libjack0 | libjack-0.116, so > it can be installed with both jackd versions but still fetches libjack0 > on buildds. > > If there are better approaches, please let me know. How about making jackd2 provide a binary package 'libjack-jackd2-dev' that conflicts with libjack-dev? -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] jackd2 packaging branch, master, updated. debian/1.9.5.dfsg-13-18-g7c7e31a
On Tue, Jun 15, 2010 at 01:35:54PM +, adiknoth-gu...@users.alioth.debian.org wrote: > The following commit has been merged in the master branch: > commit 0732d192e10a578b76d9075cdf0136445cae6304 > Author: Adrian Knoth > Date: Tue Jun 15 14:38:26 2010 +0200 > > Drop libjack-dev from jackd2. > > Only jackd1 provides the dev package. Huu, this will result in a major usability issue. While it's fine for the buildds to always use jackd1, it's inconvenient for users who want to run jackd2 AND compile some jack apps on their own. It's a rather common use case, and given that jackd2 will be the default in squeeze, we need to address this issue. Is there a well-known approach? If not, here are the facts: * libjack-dev header files are fine also for jackd2 users * /usr/lib/pkgconfig/jack.pc: Dunno. Probably ok. * /usr/lib/libjack(server).a: Does anybody care? * /usr/lib/libjack(server).so are two symlinks to the full (package specific) version number, e.g., libjack.so.0.0.28. As long as jackd1 and jackd2 don't differ in the SOVERSION, we could manually symlink libjack.so->libjack.so.0 instead. I guess libjack-dev then needs to depend on libjack0 | libjack-0.116, so it can be installed with both jackd versions but still fetches libjack0 on buildds. If there are better approaches, please let me know. TIA -- mail: a...@thur.de http://adi.thur.de PGP/GPG: key via keyserver ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
