Gentoo Archives: gentoo-user

From: Jude DaShiell <jdashiel@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user]
Date: Sat, 10 Oct 2020 16:09:46
Message-Id: alpine.NEB.2.23.451.2010101207110.26511@panix1.panix.com
In Reply to: Re: [gentoo-user] by John Covici
1 On Sat, 10 Oct 2020, John Covici wrote:
2
3 > Date: Sat, 10 Oct 2020 11:52:04
4 > From: John Covici <covici@××××××××××.com>
5 > Reply-To: gentoo-user@l.g.o
6 > To: gentoo-user@l.g.o
7 > Subject: Re: [gentoo-user]
8 >
9 > On Sat, 10 Oct 2020 10:00:04 -0400,
10 > Jude DaShiell wrote:
11 > >
12 > > On Sat, 10 Oct 2020, Ashley Dixon wrote:
13 > >
14 > > > Date: Sat, 10 Oct 2020 08:17:07
15 > > > From: Ashley Dixon <ash@××××××××××.uk>
16 > > > Reply-To: gentoo-user@l.g.o
17 > > > To: gentoo-user@l.g.o
18 > > > Subject: Re: [gentoo-user]
19 > > >
20 > > > On Sat, Oct 10, 2020 at 07:45:14AM -0400, Jude DaShiell wrote:
21 > > > > I didn't emerge portaudio or pulseaudio before emerging espeak so will
22 > > > > have to reemerge espeak to pick those USE variables up.
23 > > >
24 > > > You don't *need* portaudio or Pulse, but then you'll only be able to create WAV
25 > > > files, and not have the audio played live [1]. The developers should probably
26 > > > set one of them to be enabled by default in IUSE, since only creating WAV files
27 > > > is a very unusual use-case for a screen-reader.
28 > > >
29 > > > > Another mistake I made was emerging espeak before emerging
30 > > > > sys-kernel/gentoo-sources but since I'll have to reemerge, the
31 > > > > sys-kernel/gentoo-sources package has been emerged on the system now. The
32 > > > > right order of operations here is critical!
33 > > >
34 > > > That's quite rare for Gentoo; Portage usually takes care of all that type of
35 > > > thing without requiring manual user interaction. The gentoo-sources ebuild
36 > > > doesn't really do much, aside from calling a couple of functions in the
37 > > > `kernel-2` eclass [2, 3] to extract the sources, generate the symlinks, and
38 > > > check for any potential versioning issues.
39 > > >
40 > > > Can you provide some more details? Why is the order relevant?
41 > > >
42 > > > [1] https://gitweb.gentoo.org/repo/gentoo.git/tree/app-accessibility/espeak/espeak-1.48.04-r1.ebuild#n93
43 > > > [2] https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/kernel-2.eclass#n1603
44 > > > [3] https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/kernel-2.eclass#n1005
45 > > >
46 > > >
47 > >
48 > > --
49 > >
50 > > If you have portaudio or pulseaudio and alsa in your USE variables already
51 > > then espeak will pull those in and build so it can do more than make wav
52 > > files. Same with speech-dispatcher for other screen readers. I was being
53 > > conservative with what I put in my USE variable and added things to it as
54 > > I found things out.
55 > >
56 > > I did make menuconf in /usr/src/linux and in devices->staging drivers I
57 > > found nothing to enable. Speakup got moved out of staging so that's
58 > > understandable. in device drivers->accessibility all I found was enable
59 > > app-accessibility which I turned on. Is speakup.synth=soft stored in the
60 > > runtime driver for espeak now?
61 > >
62 > >
63 > >
64 >
65 > In kernel 5.4.69 its in staging, I would suggest you get that shource
66 > -- no need to get the absolutely latest driver.
67 >
68 >
69
70 --
71
72 Nothing in staging and console braille on output device was all that was
73 in accessibility.
74 It's time for lunch, this is too difficult without it and probably will be
75 too difficult after lunch too.