app-portage/eix-0.8.1 works great. But it seems have some wrong order of constructor initialize or so (try w/ -Wall). I've poked it to fix, and I'll submit my patches. However, I'm not C++ coder. So, if maintainers or devs have a time to review'n'test and these are real fix, please consider to merge.
Created attachment 101943 [details, diff] a patch to silence some warnings for app-portage/eix-0.8.1
Created attachment 101946 [details] summary of this patch I'll post pre-patched/post-patched warning snippet of, "ebuild eix-0.8.1.ebuild compile 1> /dev/null 2>/warnings" These logs comes from w/ USE="sqlite" CXXFLAGS="-Os -Wall".
Thanks for your patches. Good work. I merged them with eix' current svn trunk with the only exception that the two "int" -> "unsigned int" conversions were turned into conversions to string::size_type and vector<string>::size_type, respectively, which I guess is probably somewhat cleaner. Since it appears that you created the patches manually in several steps (they needed different -p? numbers) some suggestion: If you patch an svn hosted project like eix, it is probably simpler for you (and the maintainer) if you call (in the eix example) svn co http://dev.croup.de/repos/eix/trunk to create your local copy of the trunk directory (later on, "svn update" in this directory suffices), make your patches and testing in this directory and then simply call "svn diff" in this directory to create the patches.
(In reply to comment #3) > Thanks for your patches. Good work. I'd have to say exactly same line, your quick response really rocks. :) > I merged them with eix' current svn trunk with the only exception that the two > "int" -> "unsigned int" conversions were turned into conversions to > string::size_type and vector<string>::size_type, respectively, which I guess is > probably somewhat cleaner. ACK. > Since it appears that you created the patches manually in several steps (they > needed different -p? numbers) some suggestion: If you patch an svn hosted > project like eix, it is probably simpler for you (and the maintainer) if you > call (in the eix example) > svn co http://dev.croup.de/repos/eix/trunk > to create your local copy of the trunk directory (later on, "svn update" in > this directory suffices), make your patches and testing in this directory and > then simply call "svn diff" in this directory to create the patches. I'm really new to use of Subversion b/c only what I use was Mercurial. Thanks for your suggestion, memorized.
Since eix-0.8.2 contains the patches and is now officially released, I mark this bug as "resolved upstream".
