I would like to request an ebuild for Gtk-Gnutella - The Graphical Unix Gnutella Client, version 0.96.2, released 17 October 2006. It would be beneficial if this ebuild could include the patch from Bug #144668
Please note that the fix for bug #144668 should not be included in gtk-gnutella 0.96.2, because the problem is solved upstream.
Created attachment 100820 [details] gtk-gnutella-0.96.2.ebuild An updated ebuild for gtk-gnutella 0.96.2. Notable changes: * Depends on either bison or yacc (instead of always requiring yacc) * Has three new use flags: gnutls for secure Gnutella connections, ipv6 for IPv6-based Gnutella connections, and sqlite3 for using more optimized storage for the spam file in gtkg CVS.
ebuild works great on amd64. Any idea when this will enter the main portage tree?
Created attachment 101067 [details] gtk-gnutella-0.96.2.ebuild Here is an updated ebuild that fixes a few more things: - remove unused gnome use flag - remove dependency on yacc or bison (it's not needed because the generated files are distributed and used) - add dependencies on zlib and gtk+
> - add dependencies on zlib The normal ebuild policy is to *ignore* that dependency, because zlib is assumed to be installed (as is e.g. app-arch/gzip and sys-devel/gcc).
Created attachment 101615 [details] gtk-gnutella-0.96.3.ebuild I've updated the ebuild for the recent release of gtk-gnutella 0.96.3, which contains a number of important bug fixes.
Created attachment 101656 [details] gtk-gnutella-0.96.3.ebuild I've updated the ebuild to remove the ipv6 flag after discussing this with upstream. ipv6 support should be autodetected and enabled if present. The ability to remove it in the Configure script is really only there to avoid building with ipv6 on systems with a buggy or plainly broken ipv6 implementation. It used to be the case that ipv4-only was more optimized than ipv4 and ipv6, but this is no longer the case, and the ipv4-only code-paths are considered to be more buggy.
The question I have about this is suppose one migrates from an IPv4 only system to one supporting IPv6. emerge -avuDN world will not recomplile gtk-gnutella if it does not have an ipv6 use flag. The user must then complile it manually or wait for a version release. (In reply to comment #7) > Created an attachment (id=101656) [edit] > gtk-gnutella-0.96.3.ebuild > > I've updated the ebuild to remove the ipv6 flag after discussing this with > upstream. ipv6 support should be autodetected and enabled if present. The > ability to remove it in the Configure script is really only there to avoid > building with ipv6 on systems with a buggy or plainly broken ipv6 > implementation. It used to be the case that ipv4-only was more optimized than > ipv4 and ipv6, but this is no longer the case, and the ipv4-only code-paths are > considered to be more buggy. >
I think the scenario in comment #8 is fairly unlikely. The code that gets enabled depends on whether the underlying OS supports IPv6, not on whether there actually is IPv6 connectivity. As far as I know most OS currently in use already support IPv6 for quite some time, so only really old systems won't have this support. The chance that you can carry over your installation from such an old system without reinstalling doesn't seem to be very big to me. If there are systems without (working) IPv6 still actively supported for Gentoo than we should reconsider adding the IPv6 USE flag for this reason. If the IPv6 support is compiled in and you get IPv6 connectivity later then you can just enable the IPv6 parts in the gtk-gnutella interface.
Actually, the scenario I mentioned above happened to me. When I first build my system, I did not enable IPv6 support. When I realized that I was able to get IPv6 connectivity, I recompiled my kernel with IPv6 support, enabled the ipv6 use flag, and rebuild all affected packages. If gtk-gnutella drops this use flag, it would not have been rebuilt with the rest of the packages, keeping IPv6 support out of the application.
(In reply to comment #10) > keeping IPv6 support out of the application. Wrong. Look: "ipv6 support should be autodetected and enabled if present."
Are you saying that it will just magically recompile itself when it autodetects IPv6 support, or is it going to compile with IPv6 support whether my system has capability or not?
Whether or not you enable IPv6 support in the kernel does not change the fact that your system knows about and provides the right include files and definitions for IPv6 as part of the kernel and libc. So gtk-gnutella uses those to include support for IPv6. If you later decide to include IPv6 support in the kernel then gtk-gnutella can use it right away, there is no need for recompilation. The problem mentioned in comment #8 only happens when your OS doesn't know about IPv6 at all, or its definitions of IPv6 are broken. For example, you are still running Linux 0.99 with libc5 (hypothetical example as I can't remember when IPv6 became supported in the kernel and glibc).
Understood; I stand corrected. I just wanted to be absolutly certain about the issue. Thank you for your explaination. :)
The gtk-gnutella-0.96.3.ebuild works fine. Fixes the nls bug also [ http://bugs.gentoo.org/show_bug.cgi?id=144668 ].
I finally got fed up with the crashing of 0.96.1 and installed 0.96.3 using the ebuild attached here. The emerge worked and the program works. We'll see if it fixes the crashing though.
(In reply to comment #15) > The gtk-gnutella-0.96.3.ebuild works fine. Fixes the nls bug also [ > http://bugs.gentoo.org/show_bug.cgi?id=144668 ]. When will this ebuild become available in portage?
net-p2p people: if there is currently no active maintainer for gtk-gnutella I'd be happy to take over maintainership.
(In reply to comment #18) > net-p2p people: if there is currently no active maintainer for gtk-gnutella I'd > be happy to take over maintainership. > I second the motion. This is a great app - would be a shame to see it slip away. You have my vote.
(In reply to comment #18) > net-p2p people: if there is currently no active maintainer for gtk-gnutella I'd > be happy to take over maintainership. > You have my blessing. Just join the herd and you can fix other stuff too :)
Great. I expect to add the new ebuild to portage this weekend.
I've just added gtk-gnutella 0.96.3 to portage. Thanks for the feedback everyone.
