From owner-freebsd-ports@FreeBSD.ORG Fri Mar 21 01:07:08 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96DDEED1 for ; Fri, 21 Mar 2014 01:07:08 +0000 (UTC) Received: from mail.egr.msu.edu (gribble.egr.msu.edu [35.9.37.169]) by mx1.freebsd.org (Postfix) with ESMTP id 6C364F9A for ; Fri, 21 Mar 2014 01:07:07 +0000 (UTC) Received: from gribble (localhost [127.0.0.1]) by mail.egr.msu.edu (Postfix) with ESMTP id C7B402CFE6 for ; Thu, 20 Mar 2014 21:07:06 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mail.egr.msu.edu ([127.0.0.1]) by gribble (gribble.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZE-X5zKbWJK for ; Thu, 20 Mar 2014 21:07:06 -0400 (EDT) Received: from EGR authenticated sender Message-ID: <532B90B9.4080003@egr.msu.edu> Date: Thu, 20 Mar 2014 21:07:05 -0400 From: Adam McDougall User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: Libiconv confusion on 10.0-RELEASE References: <532B155B.4000108@rcn.com> <20140320195456.6141bcaf@tiger2008.drpetervoigt.private> In-Reply-To: <20140320195456.6141bcaf@tiger2008.drpetervoigt.private> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Mar 2014 01:07:08 -0000 On 03/20/2014 14:54, Dr. Peter Voigt wrote: > Thanks on feedback to all. > > Meanwhile I've read a lot about iconv and to be honest, things are > becoming even less clear. I am having not enough experience with FreeBSD > to completely judge the situation. But obviously replacement of the > ports version of iconv is still an ongoing process somehow related to > 10.0-RELEASE. > > Besides the full list of affected ports I would like to know, if the > 11 ports on my 10.0-RELEASE system currently depending on > converters/libiconv all really have to. Or could they be built against > the base iconv? My attempts so far to rebuild them with > the /usr/ports/UPDATING advice was not successful. My feeling says > that information about iconv in /usr/ports/UPDATING is not complete. > > Regards, > Peter "Late" in the release cycle, libiconv was added to the base in 10. At the time, libiconv in base was intended to fully replace the one in ports on 10. For people who already had an earlier version of FreeBSD 10 or less were encouraged to recompile ports to use the libiconv in base and get rid of the port. Later on after 10 was released and people started using applications that use libiconv from base, some features were discovered missing or working improperly and some ports were modified to pull in libiconv from ports, and the libiconv from ports was modified to stop whining at users to remove it on 10. In short, if you installed 10.0-RELEASE, don't pay any attention to libiconv unless you are having specific problems. Do not try to fight ports from using libiconv from ports, they are using that version for a good reason. You don't really have a choice. Just relax and go with the flow. Don't try to force things to use one or the other.