Summary: | mail-client/evolution-3.16.3: : e-day-view.c:3129:5: error: implicit declaration of function 'gtk_drag_cancel' [-Werror=implicit-function-declaration] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | joakim.tjernlund |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge log
package history |
Description
Toralf Förster
2015-06-11 13:35:51 UTC
Created attachment 404950 [details]
package history
What version of gtk+ are you using? IIRC gtk_drag_cancel() was introduced in gtk+ only recently, we may need to adjust evolution's dependencies. (In reply to Alexandre Rostovtsev from comment #2) Never mind, you have it in the attached history already, 3.14.13. And we need 3.16 for gtk_drag_cancel() Upstream has addressed this in https://git.gnome.org/browse/evolution/commit/?id=b87d23685ae2bcc51636aa08284d96050614e7f5 by making the dependency on gtk+-3.16 automagic. I think we should simply make it explicit. + 11 Jun 2015; Alexandre Rostovtsev <tetromino@gentoo.org> + evolution-3.16.3.ebuild: + Require >=gtk+-3.16 (bug #551774, thanks to Toralf Förster). (In reply to Alexandre Rostovtsev from comment #4) > Upstream has addressed this in > https://git.gnome.org/browse/evolution/commit/ > ?id=b87d23685ae2bcc51636aa08284d96050614e7f5 by making the dependency on > gtk+-3.16 automagic. > > I think we should simply make it explicit. > > + 11 Jun 2015; Alexandre Rostovtsev <tetromino@gentoo.org> > + evolution-3.16.3.ebuild: > + Require >=gtk+-3.16 (bug #551774, thanks to Toralf Förster). Please don't, evolution 3.16 and 3.17 works fine with current 3.14 and it would be nice if one could still use Evo without unstable gnome stuff. We apply this policy all the time. We try to avoid automagic support for one version or another of a library as much as possible just like we avoid automagic dependencies. This limits having to figure out why a feature is broken with two identical setup because the user updated the library later on keeping the broken implementation. (In reply to Gilles Dartiguelongue from comment #6) > We apply this policy all the time. We try to avoid automagic support for one > version or another of a library as much as possible just like we avoid > automagic dependencies. This limits having to figure out why a feature is > broken with two identical setup because the user updated the library later > on keeping the broken implementation. I would argue that this is a special case, there is no good release of evolution that will work well with current gtk as there is no evolution for gtk/gnome 3.14 I guess that is why upstream still maintains compatibility with gtk 3.14 Please restore gtk 3.14 dependency, at least until gtk3.16 is stable. |