From: William Hubbs <williamh@gentoo.org>
To: gentoo-accessibility@lists.gentoo.org
Subject: Re: [gentoo-accessibility] Introducing myself, with a few short questions
Date: Fri, 5 Oct 2007 21:42:31 -0500 [thread overview]
Message-ID: <20071006024231.GA21461@linux1> (raw)
In-Reply-To: <200710050906.26459.sonofthejedi@xtra.co.nz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Robert,
On Fri, Oct 05, 2007 at 09:06:26AM +1300, Robert Willam Grieve wrote:
> In the past I've tryed everything to get speech synthesis working
> to it's full potential. I got wolf to teach me how to do livecd
> builds, and I've done a couple, and I'm pretty close to getting
> speak-up in a live cd env, but, then they pulled it from the
> main kernel, so now I would like to know, are there any ways I
> can continue working on this, as put the last kernel build in an
> overlay, make a patch ebuild to retrieve the patches etc.
If you use the 2007.0 live cd, speakup is included, but not
speech-dispatcher or espeak.
The reason speakup was pulled from gentoo-sources was that it was not at
the time compatible with version 2.6.22 of the kernel. Upstream is working on making it compatible with newer kernels. However, AFAIK, speakup is still part of earlier versions of gentoo-sources.
I don't know the current status, but work is going on to clean up
speakup code so that it can be merged into the mainline kernel at some
point.
> If I can solve the problem of how to get the kernel to build with
> the code in again, then tht will help, as I have already got
> sftsyn type working before. I also want to make a meta-package
> which will pull in all bits that we need for the default sftsyn
> setup, and get them all configured, so I can then say, in the
> livecd emerge gentoo-sftsyn, and get a default with say, a
> kernel patch, espeak, speech-dispatcher and all the services
> maybe added to /etc/init.d/
Speech-dispatcher is really the only thing that needs something in
/etc/init.d, and espeak is a dependency for speech-dispatcher. I don't
see what you want to do with a meta-package. Can you give me a better
idea?
Thanks,
- --
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHBvYXblQW9DDEZTgRAvcsAJsHt994CjYwZ3MA+XOi+EiLtIzcVwCeKg24
7MuRgezau6vlYdfQe7rZEZM=
=WcOU
-----END PGP SIGNATURE-----
--
gentoo-accessibility@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-06 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1191296066-18f37aa6-mlmmj-5e667c1b@6c8e3472.plonk>
2007-10-04 20:06 ` [gentoo-accessibility] Introducing myself, with a few short questions Robert Willam Grieve
2007-10-06 2:42 ` William Hubbs [this message]
2007-10-07 21:42 Robert Greive
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071006024231.GA21461@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-accessibility@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox