On Sat, 10 Oct 2020 10:00:04 -0400,
Jude DaShiell wrote:
>
> On Sat, 10 Oct 2020, Ashley Dixon wrote:
>
> > Date: Sat, 10 Oct 2020 08:17:07
> > From: Ashley Dixon <a...@suugaku.co.uk>
> > Reply-To: gentoo-user@lists.gentoo.org
> > To: gentoo-user@lists.gentoo.org
> > Subject: Re: [gentoo-user]
> >
> > On Sat, Oct 10, 2020 at 07:45:14AM -0400, Jude DaShiell wrote:
> > > I didn't emerge portaudio or pulseaudio before emerging espeak so will
> > > have to reemerge espeak to pick those USE variables up.
> >
> > You don't *need* portaudio or Pulse, but then you'll only be able to create
> > WAV
> > files, and not have the audio played live [1]. The developers should
> > probably
> > set one of them to be enabled by default in IUSE, since only creating WAV
> > files
> > is a very unusual use-case for a screen-reader.
> >
> > > Another mistake I made was emerging espeak before emerging
> > > sys-kernel/gentoo-sources but since I'll have to reemerge, the
> > > sys-kernel/gentoo-sources package has been emerged on the system now. The
> > > right order of operations here is critical!
> >
> > That's quite rare for Gentoo; Portage usually takes care of all that
> > type of
> > thing without requiring manual user interaction. The gentoo-sources
> > ebuild
> > doesn't really do much, aside from calling a couple of functions in
> > the
> > `kernel-2` eclass [2, 3] to extract the sources, generate the symlinks,
> > and
> > check for any potential versioning issues.
> >
> > Can you provide some more details? Why is the order relevant?
> >
> > [1]
> > https://gitweb.gentoo.org/repo/gentoo.git/tree/app-accessibility/espeak/espeak-1.48.04-r1.ebuild#n93
> > [2]
> > https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/kernel-2.eclass#n1603
> > [3]
> > https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/kernel-2.eclass#n1005
> >
> >
>
> --
>
> If you have portaudio or pulseaudio and alsa in your USE variables already
> then espeak will pull those in and build so it can do more than make wav
> files. Same with speech-dispatcher for other screen readers. I was being
> conservative with what I put in my USE variable and added things to it as
> I found things out.
>
> I did make menuconf in /usr/src/linux and in devices->staging drivers I
> found nothing to enable. Speakup got moved out of staging so that's
> understandable. in device drivers->accessibility all I found was enable
> app-accessibility which I turned on. Is speakup.synth=soft stored in the
> runtime driver for espeak now?
>
>
>
In kernel 5.4.69 its in staging, I would suggest you get that shource
-- no need to get the absolutely latest driver.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
cov...@ccs.covici.com
