Tracking upstream porting effort.
Upstream currently offers developer preview gimp-2.99 branch that already depends on gtk+:3. Gentoo portage tree provides 2.99.2-r*, 2.99.4 and 9999 ebuilds for that branch as SLOT=0/3.
I read the mailing and now see that this issue is due to "GTK-2 EOL and removal" plans. I'm afraid gimp 2.10.x branch never will ported to gtk+:3 so there are two main options: * hold gimp-2.10.x (gtk+:2) as long as possible until upstream will release the final gimp-3.0. * drop gimp 2.10.x branch in favor of 2.99.x developer branch that currently is non-keyworded before gimp-3.0 release.
Don't worry. We can wait for the 3.0 release.
(In reply to Sergey Torokhov from comment #2) > I read the mailing and now see that this issue is due to "GTK-2 EOL and > removal" plans. I'm afraid gimp 2.10.x branch never will ported to gtk+:3 so > there are two main options: > * hold gimp-2.10.x (gtk+:2) as long as possible until upstream will release > the final gimp-3.0. > * drop gimp 2.10.x branch in favor of 2.99.x developer branch that currently > is non-keyworded before gimp-3.0 release. My biggest problem is that I can't scan from gtk3 gimp because there is no upstream activity on switching sane-frontends aka xsane to gtk3. Or do you know a working scan plugin?
Do you strictly need scan functionality from within gimp or can you just use an external tool?
(In reply to Andreas Sturmlechner from comment #5) > Do you strictly need scan functionality from within gimp or can you just use > an external tool? I can use an external tool. Did try libksane based skanlite and kolourpaint. But scan functionality from within gimp would be less steps. Time, (processing)work, maybe picture quality related reasons.
