So, I've wasted time trying to bump app-editors/beaver to latest version 0.3.1 designed for GTK+-2.0, it's 4 years old release and upstream is unavailable. I got it built after passing -DGTK_ENABLE_DEPRECATED flags but it just plain segfaults. Current version in tree is even older, using GTK+-1.2.. however it still runs. If upstream doesn't care, neither should we. Just punt it, and if they resurrect in future, we can add an updated & fixed GTK+-2.0 version.
Created attachment 128478 [details] beaver-0.3.1.ebuild Ebuild using GTK+-2.0, builds after hacking DISABLE_DEPRECATED functions to ENABLE_DEPRECATED ones. Doesn't run.
(In reply to comment #1) > Created an attachment (id=128478) [edit] > beaver-0.3.1.ebuild > > Ebuild using GTK+-2.0, builds after hacking DISABLE_DEPRECATED functions to > ENABLE_DEPRECATED ones. Doesn't run. > Err, the append-flags -Wall -O3 -funroll-loops -fomit-frame-pointer is there just because I tried upstream flags.. they prefer these ones. Feel free to remove it from the test ebuild, result is still same.
+1, I don't see any point in keeping stuff that's unmaintained both upstream and in Gentoo and depends on obsolete, unmaintained gtk+-1 in the tree.
Created attachment 128479 [details, diff] beaver-0.3.1-malloc.patch Some patches from FreeBSD before they decided to punt it.. Still useless with this.
+1
gone
