Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 640066 - app-misc/gourmet: disable optional support relying on dead gnome2 python bindings
Summary: app-misc/gourmet: disable optional support relying on dead gnome2 python bind...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Joe Sapp (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: gnome2-python-removal
  Show dependency tree
 
Reported: 2017-12-06 15:06 UTC by Pacho Ramos
Modified: 2018-02-06 07:59 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pacho Ramos gentoo-dev 2017-12-06 15:06:19 UTC
gnome2 python bindings are dead for ages, this package only relies on them with "spell" USE flag. Could that support be disabled then?

Thanks
Comment 1 Joe Sapp (RETIRED) gentoo-dev 2018-02-03 14:17:06 UTC
I think that's reasonable, but let me look into it.
Comment 2 Joe Sapp (RETIRED) gentoo-dev 2018-02-03 14:38:47 UTC
Is there a reason besides age?  gtkspell is used in the spell check plugin.  If there were an alternative maybe I could implement it.
Comment 3 Joe Sapp (RETIRED) gentoo-dev 2018-02-03 14:41:48 UTC
Looks like https://github.com/koehlma/pygtkspellcheck is a potential replacement, but I don't have the time to try to get this into the tree.  It only appears to require pyenchant, which is in the tree so it shouldn't be difficult.
Comment 4 Joe Sapp (RETIRED) gentoo-dev 2018-02-06 07:52:18 UTC
If gnome2 python bindings are going to be removed from the tree, we can remove support for the spellcheck plugin from gourmet.  Alternatively, if there's work upstream and alternatives in portage, we could implement that.  Until either of these happen, I'm going to mark this is as an upstream problem.
Comment 5 Pacho Ramos gentoo-dev 2018-02-06 07:59:39 UTC
Did you report this to upstream to at least let us track the issue there?