just a new ettercap version with the new gtk2 interface available .... this ebuild worked fine for me .. but i dont know how god the gtk2 use variable handling is.. # Copyright 1999-2002 Gentoo Technologies, Inc. # Distributed under the terms of the GNU General Public License v2 # $Header: /home/cvsroot/gentoo-x86/net-analyzer/ettercap/ettercap- 0.6.7.ebuild,v 1.7 2002/12/15 11:58:45 bjb Exp $ IUSE="ssl gtk2" S=${WORKDIR}/${P} DESCRIPTION="Ettercap is a multipurpose sniffer/interceptor/logger for switched LAN." SRC_URI="http://ettercap.sourceforge.net/download/${P}.tar.gz" HOMEPAGE="http://ettercap.sourceforge.net" SLOT="0" LICENSE="GPL-2" KEYWORDS="x86 sparc alpha" DEPEND="sys-libs/ncurses ssl? ( dev-libs/openssl ) ( gtk2? >=x11-libs/gtk+-2* ) ( gtk2? >=dev-libs/glib-2* )" src_compile() { local myconf use ssl && myconf="${myconf} --enable-https" use gtk2 && myconf="${myconf} --enable-devel --enable-gtk" ./configure --host=${CHOST} --prefix=/usr --enable-ncurses --enable- plugins ${myconf} assert make CFLAG="${CFLAGS} -funroll-loops -fomit-frame-pointer -Wall" || die make CFLAG="${CFLAGS} -funroll-loops -fomit-frame-pointer -Wall" plug- ins || die } src_install() { make prefix=${D}/usr MANDIR=${D}/usr/share/man complete_install || die rm ${D}/usr/share/doc/${P}/ettercap.fr.8.in.gz gzip ${D}/usr/share/doc/${P}/* }
And now there is an even newer version available - 0.6.a is out.
hmm .. the ebuild attached is rather ugly, especially because it was based on a pretty bad ebuild in the first place. and what is with the versioning 0.6.a? are they trying to be funny? the deps are also wrong in this one .. should be: gtk2? ( >=x11-libs/gtk+-2 >=dev-libs/glib-2 ) if the bug reporter or anyone would like to submit a new ebuild based on the newer 0.6.9.ebuild and attach it following the ebuild submission howto guidelines that would be very helpful.
i wouldnt recommend enabling gtk2 support just yet, it is too crashy. The versioning is indeed silly, but i would suggest we just move to .10 and replace P in the ebuild, works just fine.
although this isn't really a gnome bug, i've bumped this to 0.6.10 (0.6.a) and did not put in the optional gtk interface.