|
»
« Return to Thread: Re: jack2's dbus name
Re: [LAD] jack2's dbus name
by Fernando Lopez-Lezcano
::
Rate this Message:
On Mon, 2009-06-15 at 22:12 -0400, Paul Davis wrote:
> On Mon, Jun 15, 2009 at 6:25 PM, Fons Adriaensen<fons@...> wrote:
> >
> > I'll repeat this: if dbus becomes a dependency for Jack, I will
> > fork Jack.
>
> And I'll repeat: JACK will not depend on non-POSIX interfaces for any
> essential functions unless the platform requires it, which it does not
> in this case.
>
> Good grief, Fons. Get a grip. We're trying to figure out how to make a
> system installed by more and more distributors can play nice with
> JACK. It has nothing to do with JACK functionality, and JACK is never
> going to "depend" on DBus. What more do I have to do to make this
> clear?
>
> You'd prefer that we spend whatever development time we have for JACK
> on *another* plugin system for the ALSA backend, or that we just do
> the simple thing and provide ./configure --with-alsa-dbus-negotiation
> so that distributors can make this work if they are building a package
> that is intended to run on a PulseAudio-equipped machine?
I don't remember if I have explicitly expressed my preferences with my
packager's hat on.
What I want to be able to do as a packager is, I think, simple (and I
want the same thing as a user!).
I want users to be able to choose whether to run jackd as before (ie: no
dbus), or run jackd with a dbus connection. I don't want to force them
to use either mode. The choice could be made with a jackd runtime switch
(in which case I would like to be able to select at compile time which
mode is the default), or it could be made by installing an additional
package (in which case installing an additional package would magically
add the dbus functionality and removing it would remove that
functionality[*]). I think I would prefer a runtime switch.
In other words I want the possibility to transition from one mode to the
other and back, and I want that possibility to be in the hands of each
user and not just in my hands as a packager.
I don't care that much about how this is accomplished.
-- Fernando
[*] BTW, "installing an additional package" means not modifying any of
the files of the original base jack-audio-connection-kit package but
rather adding something (shared library?) that is recognized by the
existing jackd and automatically adds the functionality.
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> On Mon, Jun 15, 2009 at 6:25 PM, Fons Adriaensen<fons@...> wrote:
> >
> > I'll repeat this: if dbus becomes a dependency for Jack, I will
> > fork Jack.
>
> And I'll repeat: JACK will not depend on non-POSIX interfaces for any
> essential functions unless the platform requires it, which it does not
> in this case.
>
> Good grief, Fons. Get a grip. We're trying to figure out how to make a
> system installed by more and more distributors can play nice with
> JACK. It has nothing to do with JACK functionality, and JACK is never
> going to "depend" on DBus. What more do I have to do to make this
> clear?
>
> You'd prefer that we spend whatever development time we have for JACK
> on *another* plugin system for the ALSA backend, or that we just do
> the simple thing and provide ./configure --with-alsa-dbus-negotiation
> so that distributors can make this work if they are building a package
> that is intended to run on a PulseAudio-equipped machine?
I don't remember if I have explicitly expressed my preferences with my
packager's hat on.
What I want to be able to do as a packager is, I think, simple (and I
want the same thing as a user!).
I want users to be able to choose whether to run jackd as before (ie: no
dbus), or run jackd with a dbus connection. I don't want to force them
to use either mode. The choice could be made with a jackd runtime switch
(in which case I would like to be able to select at compile time which
mode is the default), or it could be made by installing an additional
package (in which case installing an additional package would magically
add the dbus functionality and removing it would remove that
functionality[*]). I think I would prefer a runtime switch.
In other words I want the possibility to transition from one mode to the
other and back, and I want that possibility to be in the hands of each
user and not just in my hands as a packager.
I don't care that much about how this is accomplished.
-- Fernando
[*] BTW, "installing an additional package" means not modifying any of
the files of the original base jack-audio-connection-kit package but
rather adding something (shared library?) that is recognized by the
existing jackd and automatically adds the functionality.
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
« Return to Thread: Re: jack2's dbus name
| Free embeddable forum powered by Nabble | Forum Help |
