Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 470934 - app-accessibility/speech-dispatcher-0.8-r2 stabilization request
Summary: app-accessibility/speech-dispatcher-0.8-r2 stabilization request
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: William Hubbs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-22 02:18 UTC by Mike Gilbert
Modified: 2013-05-22 17:32 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Gilbert gentoo-dev 2013-05-22 02:18:07 UTC 
www-client/chromium-27 needs at least app-accessibility/speech-dispatcher-0.8.

Please stabilize ASAP.
Comment 1 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2013-05-22 02:43:55 UTC 
(In reply to comment #0)
> www-client/chromium-27 needs at least
> app-accessibility/speech-dispatcher-0.8.
> 
> Please stabilize ASAP.

Given that it changes API in an incompatible way, it may be harder to do.

Another option is to just remove the 0.8 requirement from chromium-27 (and add a <0.8 dependency) - I'll test and do that unless stabilizations happens earlier than that.
Comment 2 Mike Gilbert gentoo-dev 2013-05-22 02:58:16 UTC 
Ah, this brings us back to the conditional patching issue again. I still think that's the easy/reasonable solution here.
Comment 3 Paweł Hajdan, Jr. (RETIRED) gentoo-dev 2013-05-22 17:32:22 UTC 
(In reply to comment #2)
> Ah, this brings us back to the conditional patching issue again. I still
> think that's the easy/reasonable solution here.

Well, chromium-28.x will only need a conditional src_configure code instead of a conditional patch. While the latter is not acceptable, I'm totally fine with conditional src_configure code in chromium-28.x.

Let's close this bug for now - it will be easier to handle at chromium-28.x time.