Date: Thu, 25 Mar 2004 14:40:16 +0100 From: Guido Berhoerster <ich@guido-berhoerster.org> To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, f-ports <freebsd-ports@FreeBSD.org> Subject: Re: ports/64558: Update x11-wm/fvwm2-devel, PATCH Message-ID: <20040325134016.GA1035@hal.privat.lan> In-Reply-To: <20040324200203.GA962@moo.holy.cow> References: <20040322063720.12826A5AD@moo.holy.cow> <200403220640.i2M6eDIh095068@freefall.freebsd.org> <20040322065009.GA91460@moo.holy.cow> <20040324200203.GA962@moo.holy.cow>
next in thread | previous in thread | raw e-mail | index | archive | help
I don't have time to test the patch right now but I'd like to add two things to this PR: FVWM 2.4.18 and 2.5.10 were released due to security vulnerabilities in, see http://securitytracker.com/alerts/2004/Jan/1008781.html http://www.securityfocus.com/bid/9161 The mentioned problem with FvwmGtk occurs because the port does not turn off GTK-support correctly. So if x11-toolkits/gtk12 is installed it will still be detected and FvwmGtk will be installed but not registered in pkg-plist. From INSTALL.fvwm: ----snip---- To disable autoprobing of GTK+, Imlib and GNOME libraries, use: --disable-gtktest --disable-imlibtest --without-gnome This does not turn GTK+ and Imlib support off, instead, one part of the checking, precisely compilation, is quietly considered to be passed. To disable GTK+ and Imlib support even if the corresponding libraries are installed, try this solution: --with-gtk-prefix=/no/dir --with-imlib-prefix=/no/dir ----snap---- See also ports/59153, ports/59154. -- Guido Berhoerster ich@guido-berhoerster.org http://www.guido-berhoerster.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040325134016.GA1035>