Remove the need for dbus when compiling gtk+:3

Anon-E-moose · Last edited by Anon-E-moose on Tue Oct 29, 2019 9:48 am; edited 4 times in total

For those who don't want to pull in dbus when compiling gtk+:3 there is a way to fix it.

-------------Warning--------------
This has been added to further clarify who should use this:

If you are already using dbus for other things, then you should not use this.
This is for those people not running gnome/kde and for those who do not want to have dbus on their system.
-------------------------------------

New directions thanks to charles17 question below (much easier)

edit /etc/portage/profile/package.provided and add app-accessibility/at-spi2-atk-2.5.3
Note: if newer ebuilds require a version greater than 2.5.3 then that needs to be added.

mkdir /etc/portage/patches/x11-libs/gtk+:3 (you can specify version if you desire, but I've found the patch has worked well going back to 3.19)
copy following patch to the directory (call it what you want, a good name would be at-sp2-atk-removal.patch or atk-bridge-removal.patch)

emerge and enjoy your gtk:+3 without dbus being needed.

Ant P. · Watchman Joined: 18 Apr 2009 Posts: 6920

Seems like a lot of manual work when there's been up-to-date ebuilds with USE=accessibility in various overlays for several months.

sitquietly · Posted: Wed Oct 23, 2019 6:24 am Post subject:

Anon-E-moose · Posted: Wed Oct 23, 2019 9:33 am Post subject:

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3685

Anon-E-moose

duane · Posted: Thu Oct 24, 2019 7:35 am Post subject:

I couldn't get package.provided to work on my systems:

Anon-E-moose · Posted: Thu Oct 24, 2019 9:58 am Post subject:

duane · Posted: Thu Oct 24, 2019 3:02 pm Post subject:

Perfect Gentleman · Veteran Joined: 18 May 2014 Posts: 1255

check mv-overlay

Anon-E-moose · Posted: Thu Oct 24, 2019 3:40 pm Post subject:

Anon-E-moose · Posted: Thu Oct 24, 2019 3:44 pm Post subject:

So far I know of flussence and mv-overlay that also contain patched ebuilds for gtk+:3 ... any others?
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

duane · Posted: Fri Oct 25, 2019 1:21 am Post subject:

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3685

xanderal · Posted: Mon Oct 28, 2019 10:53 pm Post subject:

What do you guys think about this forum topic? It was referenced in the package.provided wiki entry.
When I first read about package.provided I kinda thought the same thing Genone wrote in the above topic:

Anon-E-moose · Posted: Mon Oct 28, 2019 11:04 pm Post subject:

One should never indiscriminately use package.provided.

You have to be aware of why you are putting an entry there and the ramifications of it.
In the case of at-spi2-atk and gtk:3 with the patch there is no problem.
Because if you are using at-spi2-atk for some other package, then you wouldn't use the patch or entry in package.provided, there wouldn't be a need to.

Putting something like gcc in package.provided would produce interesting results. I can think of a few packages that would be foolish to put there.

It all boils down to understanding what you're doing, why you're doing it, and the consequences (positive and negative)
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3685

Anon-E-moose · Posted: Fri Aug 28, 2020 9:25 am Post subject:

I think it unlikely that upstream gtk will accept the patch, as the patch was originally in an early version of gtk3, and they removed it the next minor bump.

But I'll see what I can do.

Edit to add: mv runs an overlay with the patches applied for gtk3 (mv-overlay)

ETA2: I was just looking at the bug report that I started a couple of years ago https://bugs.gentoo.org/669234
while it's highly unlikely that I could get upstream gtk devs to add the patch back it might be possible to push for it in gentoo itself, although it would require testing and proving that it doesn't cripple those people who do choose to install the bridge and might require someone to be the maintainer of said patch.

And even the gentoo devs misunderstood the removal of atk vs at-spi2-atk, the patch does not remove the use of atk, just the bridge part which pulls in dbus itself, so the underlying disability code is still there and working just the dbus/notification stuff is missing, and unless you're using gnome or gnome derivative, you won't care.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3685

It's been working for long time now until yesterday ...
Did someone get gtk+:3 work with USE=-atk-bridge ?

Anon-E-moose · Posted: Wed Nov 09, 2022 10:52 am Post subject:

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3685

Anon-E-moose · Posted: Wed Nov 09, 2022 2:08 pm Post subject:

I'd be tempted to stick with atk 2.38 instead of the latest.

Though, I do have

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3685

Thanks Anon-E-moose

Updated with your patch and re-added at-spi2-atk to package.provided. Still the same error.
Then, restricting dev-libs/atk to 2.38.0 finally did the trick.

Thanks again

Anon-E-moose · Posted: Wed Nov 09, 2022 3:01 pm Post subject:

Probably something to do with this (from at-spi-core)

Anon-E-moose · Posted: Wed Nov 09, 2022 3:12 pm Post subject:

Note: my original intent with this thread was to not need dbus (and associated atk bridge) with what I was running at the time (X, openbox, no kde/gnome desktop)

I have since moved on from X to wayland and there, dbus is almost a mandated necessity.

And it looks like the people that handle atk/at-spi* have merged all of that into one tarball,
which pretty much mandates dbus, if you are going to use atk* versions >= 2.46.

And again the problem does not lie with gtk+ but the atk* part.
_________________
UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland