Date: Thu, 22 Apr 2004 07:50:20 -0700 (PDT) From: Yar Tikhiy <yar@comp.chem.msu.su> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/65887: mutt and mutt-devel can silently depend on libiconv Message-ID: <200404221450.i3MEoKvt046679@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/65887; it has been noted by GNATS. From: Yar Tikhiy <yar@comp.chem.msu.su> To: Udo Schweigert <Udo.Schweigert@siemens.com> Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/65887: mutt and mutt-devel can silently depend on libiconv Date: Thu, 22 Apr 2004 18:49:19 +0400 On Thu, Apr 22, 2004 at 03:53:29PM +0200, Udo Schweigert wrote: > On Thu, Apr 22, 2004 at 17:32:57 +0400, Yar Tikhiy wrote: > >>Fix: > > An easy way is to add ``USE_ICONV=yes'' to the mutt Makefiles. > > A harder approach is to implement conditional dependencies > > within the ports framework, that is to let ports tell, > > "I could use the port foo if it were installed already; > > never mind otherwise." > > One could also choose to use the --disable-iconv option of mutt's configure. By itself it's more to amputation than to a solution :-) Mutt's using libiconv is a valuable feature for users whose native alphabet falls beyond Latin-1. And specifying --disable-iconv would inhibit mutt from using libiconv even if it is installed. Perhaps having a WITH_ICONV knob for mutt would be better. The knob function can be as follows: on - set USE_ICONV=yes off - set --disable-iconv -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404221450.i3MEoKvt046679>