From: William Hubbs <williamh@gentoo.org>
To: speakup@braille.uwo.ca
Subject: Re: Gentoo - where's speakup been put?
Date: Thu, 8 May 2008 21:22:31 -0500 [thread overview]
Message-ID: <20080509022231.GA9555@linux1> (raw)
In-Reply-To: <20080508031714.GA5580@garrettk17.lan>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Garrett,
> How will this work for those of us who want speakup in the kernel? Are
> we just going to have to stick with vanilla kernel.org kernels?
Until 2.6.26 comes out, that is what I suggest. Here is why.
Putting speakup directly into the kernel requires two patches. A patch
to the kernel sources, and a patch to the build system. If you try to
run the install script from the speakup git repository, it will attempt
to apply both patches to the kernel. But, since the patch to the
sources is already applied to gentoo-sources, this would be an error
condition.
The reason this will be different with 2.6.26 is that our patche to the
sources was accepted into the official kernel.org tree, so now we only
will patch the build system if you want to have speakup in the kernel.
Speakup itself will not be in 2.6.26, just the hooks that make it
possible for speakup to run. There are still issues to work out with
speakup before we can ask for it to be accepted into the official kernel
tree.
Does that make sense?
- --
William Hubbs
gentoo accessibility team lead
williamh@gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkgjtWcACgkQblQW9DDEZThNKgCeIlLpNbRCLwIu0xHiP/1lfNH9
3vIAn1EQaxew5Gfh4n4/+lxfAsaN7sVX
=Qkal
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Georgina Joyce
` William Hubbs
` Georgina Joyce
` William Hubbs
` Georgina Joyce
` William Hubbs
` Robert Spangler
` Garrett Klein
` William Hubbs [this message]
` Garrett Klein
` Garrett Klein
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=20080509022231.GA9555@linux1 \
--to=williamh@gentoo.org \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).