running speech-dispatcher-0.7.1 in system mode

[Trevor Saunders]

Hi


 oops, it looks like dev vcsa  might not actually be available oon all
 unix systems, but I think its still almost certianly the right way to
 find out what is on the console currently, which is the problem brltty
 and sbl want to solve.

 Trev

On Thu, Oct 07, 2010 at 04:11:47AM -0400, Trevor Saunders wrote:
> Hi,
> 
> On Wed, Oct 06, 2010 at 10:29:37AM +0200, Hynek Hanke wrote:
> > On 5.10.2010 19:16, Trevor Saunders wrote:
> > >I think all we need to do however is bring over the option, and may be
> > >another command line option or two from opentts to make this work
> > >correctly.
> > 
> >  1) Configure Speech Dispatcher to use inet_sockets
> >  2) Have a correct /etc/init.d script
> >  3) Have clients run in environment where SPEECHD_ADDRESS
> >      is correctly set.
> > 
> > This is available already. Which other options do you have
> > in mind?
> 
> I think we should port over the opentts patch to provide a default user
> and paths that are system wide to be used with a --system flag.
> Personally I think system wide is a better default especially if we
> don't allow clients to set other clients settings, but this is really an
> issue of how $distro works, so it really should be up to them.
> 
> > >what?  I don't really care, and have never looked into ubuntu's issues
> > >with pulse
> > 
> > Trev, we need to care. If major distributions use this, our
> > users use this, and they are whom we do it for.
> 
> I supose this comes down to what you believe and why you are interested
> in this project, and while I respect that other people care how speech
> dispatcher and pulse work, and I expect and hope that the people who
> deal with accessibility for ubuntu and fedora  will care about pulse and
> speech dispatcher and the interactions, I consider it neither an
> interest of mine or a responsibility of mine.  I also expect that the
> people who care about pulse will respect that not everyone wants to work
> that way and that other distros may have good reasons to want to go the
> system service route.
> 
> > >There are some clients like brltty which as Samuel has already
> > >  explained to you _can't_ work this way.
> > 
> > This is simply not true.
> 
> you can say that if you like, but it doesn't make it the case.  Would
> you like to suggest a _good_ way to do this?  From here I think opening
> dev vcsa is a pretty good way of doing things, it works on *nix and
> doesn't require putting a bunch of daemons including one everyone wants
> to be rid of between brltty / sbl and dev vcsa, which iirc was your last
> proposal.  I'm curious why you are so opposed to speech dispatcher
> running as a system service?
> 
> Trev
> 
> > 
> > Best regards,
> > Hynek Hanke
> > 
> > 
> > 
> > _______________________________________________
> > Speechd mailing list
> > Speechd at lists.freebsoft.org
> > http://lists.freebsoft.org/mailman/listinfo/speechd


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: 
<http://lists.freebsoft.org/pipermail/speechd/attachments/20101007/6eb3cdd7/attachment.pgp>