| Summary: | [PATCH] www-client/firefox-113.0.1: add accessibility use flag | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Morteza <mr.oneacer> |
| Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
| Status: | RESOLVED CANTFIX | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch to add accessibility use flag | ||
|
Description
Morteza
2023-05-23 12:07:30 UTC
Created attachment 862266 [details, diff]
Patch to add accessibility use flag
That allows you to avoid a dependency on app-accessibility/at-spi2-core -- because you want to avoid dbus? unfortunately it doesn't get rid of at-spi2-core dependency as gtk+ is hard wired to at-spi2-core, there's a patch from kisslinux to get rid of that but i don't think it will be accepted in gentoo anyhow it get rid of a runtime dependency which is a plus imo I would say conceptually this is fine, but 1) I'm kind of vary in adding more use flags to firefox, we got 'valgrind' coming soon too, 2) what _exactly_ does disabling accessibility do? Should the configure option be tied to "-dbus" instead? And as you've noted yourself, avoiding dbus with dep chains is impossible at this time, so if that's the only reason I don't see much point to this. However if there's a noticeable technical difference with enabling/disabling accessibility, then we'll figure out something. Can't do much distro-wise until it's fixed in GTK. |
